advancedProduction Debugging121 of 127
Container memory climbs for 8 to 12 hours until the OS kills it. How do you tell a heap leak from native (off-heap) memory bloat?
Tests whether you compare JVM-reported heap usage (via GC logs or JFR) against the container's actual RSS -- if RSS keeps growing while heap usage stays flat/bounded, the leak is native (direct ByteBuffers, native library allocations, Metaspace), not something a heap dump will show.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a responseNext Step
←PreviousContinue to A heap dump shows thousands of objects retained in a static cache. How do you validate whether removing it is safe?→
← Back to all Company Round Scenarios questions