Java Memory Leak Troubleshooting: How We Lost 3 Days, and Fixed It in Hours

This guide outlines the installation and configuration of yCrash, a tool for managing Java application memory issues. The author recounts a crisis where improper setup led to a three-day debugging ordeal before using yCrash effectively. Key lessons emphasize the importance of proper setup, continuous monitoring, and utilizing all available data artifacts for effective troubleshooting.

JVM Optimization in Real Systems

A Spring Boot application unexpectedly surged in JVM memory usage from 8GB to 61GB without any deployment or configuration changes. By diagnosing a ZipFile$Source memory leak with yCrash, the team identified excessive caching leading to the leak. By disabling caching and restarting the app, they reduced memory usage to 4GB effectively.

Up ↑