Precise location of a leak

Plumbr is an agent, which you can attach to any Java process.  Attached Plumbr gathers statistics about object creation and destruction within your JVM. Next, it thoroughly analyses these stats. Plumbr uses machine learning to discover patterns in your objects’ lifecycles that allow it distinguish potentially leaking objects from the normal ones.

When Plumbr is confident that it has found a memory leak, it hands you the report with all the details you need to fix the leak.

  • The line in the source code where the leaked objects were created
  • Who is currently referencing the leaked objects, preventing the garbage collection
  • And [as an experimental feature] guidelines about how to fix the leak.

Below is a sample screenshot from a report you would get from Plumbr. I guess you might agree – having this information makes fixing leaks a breeze

Memory leak location

Try it for free!

4,891
Memory Leaks discovered
$36,682,500
Saved for our customers
70 minutes
Average time for us to find the leak
Try it for free
Latest
Recommended
You cannot predict the way you die
When debugging a situation where systems are failing due to the lack of resources, you can no longer count on anything. Seemingly unrelated changes can trigger completely different messages and control flows within the JVM. Read more
Tuning GC - it does not have to be that hard
Solving GC pauses is a complex task. If you do not believe our words, check out the recent LinkedIn experience in garbage collection optimization. It is a complex and tedious task, so we are glad to report we have a whole lot simpler solution in mind Read more
Building a nirvana
We have invested a lot into our continuous integration / delivery infrastructure. As of now we can say that the Jenkins-orchestrated gang consisting of Ansible, Vagrant, Gradle, LiveRebel and TestNG is something an engineer can call a nirvana. Read more
Creative way to handle OutOfMemoryError
Wish to spend a day troubleshooting? Or make enemies among sysops? Registering pkill java to OutOfMemoryError events is one darn good way to achieve those goals. Read more