native memory leak with GarbageCollectorMXBean#getLastGcInfo

gistfile1.java

import java.lang.management.GarbageCollectorMXBean;
import java.lang.management.ManagementFactory;
import java.util.List;

public class TestMemoryLeak {

    public static void main(String[] args) throws Exception {
        while (true) {
            List<GarbageCollectorMXBean> gcMxBeans = ManagementFactory.getGarbageCollectorMXBeans();
            for (GarbageCollectorMXBean gcMxBean : gcMxBeans) {
                ((com.sun.management.GarbageCollectorMXBean) gcMxBean).getLastGcInfo();
            }
        }
    }
}

Could this just be that GC isn't having enough time to clean up as you loop through?

No, since there is nothing to clean.

Not entirely true - that List of MBeans will hang around for a while until the GC runs and evicts it. If you loop fast enough before the GC is triggered, you can wipe your memory.

Thats heap memory, not RES memory. Heap wise all is well, and things get collected.

Time to fire up YourKit!

I stumbled across this gist while looking for more information about this HotSpot bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7066129

Thats the bug I opened :)

Hah, I wondered whether that was the case—I just figured there should be a connection between the two!

@kimchy: do you have a workaround for this? Can you confirm such kind of bugs for the other MXBeans, too?