#General Debugging Advice for Memory Leak

4 messages · Page 1 of 1 (latest)

winged urchinBOT
#

When your question is answered use !solved to mark the question as resolved.

Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.

glossy veldt
#

The normal tools for debugging such things are leak sanitizer and valgrind, but neither work on Windows and chances are this .NET P-invoke stuff is not supported.

midnight hill
#

I actually need non-windows tools, this app is not meant to run on windows, but strictly Linux. Colleague was running it in WSL for this reason. Will check out valgrind.