Plumbing memory leaks in Java
summary
A practical report on fixing Java memory problems: a small Plumbr Java agent runs with the app (claimed ~25% overhead), traces object birth/death and emits one HTML report with allocation site per run so developers see which line retains unreachable objects. It targets slow, growing leaks (not synthetic tests or minute-after-start explosions), surfaces common causes—misconfigured caches, classloader/permanent-gen churn, stray threads and String/collection blowups—and runs on Mac/Windows/Linux. Pricing example shown: €150/year per seat.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:55How devs think about memory
- 7:56Java memory promises
- 11:55OutOfMemoryError causes
- 17:09Java memory leaks
- 23:17Leak examples and impact
- 28:20Leak-fighting strategies
- 31:17Diagnostic tools overview
- 36:17Our leak finder tool
- 42:40Demo and takeaways
- 43:02Q&A
related talks
02h 41mSolving Memory Leaks in the JVM
57mI bet you have a permgen leak in your application
38mMemory Efficient Java
43mTroubleshooting Memory Problems in Java Applications
21mMemory Efficient Java
51mA Healthy diet for your Java application
26mFind Java memory leaks with Heap Dumps (JDK 25)
56mJava Performance Analysis