New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
1–10 of 23 posts
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#2Really nice. I've used Yourkit profiler quite a few times to solve java memory leaks, but this automated detection seems awesome. Thanks for sharing.
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#3Really nice. I've used Yourkit profiler quite a few times to solve java memory leaks, but this automated detection seems awesome. Thanks for sharing.
How and how often do Java memory leaks actually happen? It's never stricken me as a problem. I guess some kind of global variables are involved.
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#4Really nice. I've used Yourkit profiler quite a few times to solve java memory leaks, but this automated detection seems awesome. Thanks for sharing.
How and how often do Java memory leaks actually happen? It's never stricken me as a problem. I guess some kind of global variables are involved.
You might, for example, insert an entry into a hashtable and forget to remove it. The garbage collector can't go and clean it up because it can't know whether you plan to use it or not. This way, over time, the memory usage keeps growing.
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#5Detecting memory leaks is easy: run some stress tests before deploying to production!
I mean, I don't see the use of this tool. Attach it to a live JVM to detect leaks which shouldn't be there?
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#6Detecting memory leaks is easy: run some stress tests before deploying to production! I mean, I don't see the use of this tool. Attach it to a live JVM to detect leaks which shouldn't be there?
It tends to be more complex than this for several reasons:
a) you usually cannot simulate the exact behavior of users in production environment. Users tend to be quite creative in ways they approach your workflows and your artificial tests might not catch it b) Your dev/test/staging environment is usually not a 100% replica of the production site - you might lack access to some integrated systems, have different datasets for confidentiality reasons, use virtualized machines instead of physical, etc c) Or anything else which all leads to the sad fact that oftentimes you just cannot replicate the leak in any other env than production.
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#7Neat :)
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#8Detecting memory leaks is easy: run some stress tests before deploying to production! I mean, I don't see the use of this tool. Attach it to a live JVM to detect leaks which shouldn't be there?
If you haven't had any memory leaks slip into production, you're in luck.
Also - if you can discover the leak in staging, the tool pinpoints the source of the leaks so that you don't have to waste time on reproduction, comparing heap dumps, and crawling through your code.
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#9I suppose this only detects intermittent leaks? If a particular class always leaks then this tool would have no frame of reference to detect it, right?
Re: New (revolutionary?) solution for Java memory leak discovery: Plumbr explained
#10Everytime I open a report, it hits http://app.plumbr.eu/decrypt_report with an encrypted version of the report.
Even if you don't store that information, and even if it is not really useful, you should maybe note somewhere that all the "leak" information is sent to Plumbr servers.