Community
Participate
Working Groups
In Bug 570238 and Bug 569647 I used Valgrind to hunt down some SWT native-side memory leaks. I'll use this Bug to share my tools when they're ready.
OK, I polished the scripts enough to be usable outside my lab :) Start here: https://github.com/SyntevoAlex/JavaValgrindScripts There should be sufficient explanations in the readme. @Simeon I'll be pleased if you can try that soon, so that my effort is not in vain :)
Suppressions try to remove all sorts of noise. For example, global caches in JVM/GTK are considered to be leaks, because technically they are: they are allocated and stay there until the very end. Still more suppressions could be added, but it takes time to investigate and make sure that these are not actual leaks. When in doubt, run something in a loop and see if reported leak grows or not.
(In reply to Alexandr Miloslavskiy from comment #1) > OK, I polished the scripts enough to be usable outside my lab :) > > Start here: > https://github.com/SyntevoAlex/JavaValgrindScripts > > There should be sufficient explanations in the readme. > > @Simeon I'll be pleased if you can try that soon, so that my effort is not > in vain :) Thanks a lot Alexandr! In fact we have already a memory leak in Eclipse/our product that we need to check, I'll try using the tool this and next week to hopefully find out what code is leaking.
A much faster tool: https://github.com/SyntevoAlex/JavaJemallocScripts.git @Simeon, give it a try!
