This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 240768 - 150M in com.sun.tools.jdi.VirtualMachineImpl
Summary: 150M in com.sun.tools.jdi.VirtualMachineImpl
Status: RESOLVED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 7.4
Hardware: PC Linux
: P3 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 243146 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-01-21 13:31 UTC by Tomas Hurka
Modified: 2014-04-11 18:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Hurka 2014-01-21 13:31:04 UTC
The heap dump from issue #216001 contains 150M in 19 instances of com.sun.tools.jdi.VirtualMachineImpl. It looks like some of those instances should not be held in memory. Please investigate.
Comment 1 Tomas Hurka 2014-01-21 13:33:45 UTC
Here is the heap dump:
http://www.sulweb.org/download/sparsi/heapdump.zip
Comment 2 Martin Entlicher 2014-01-21 15:24:30 UTC
Instanceof of JPDADebuggerImpl #4, #5, #7 and #12 are being held by JDI Event Control Thread. I do not think we can do anything about that. All respective instances of VirtualMachineImpl have shutdown = true, that means that either dispose() or exit() was called. The fact, that four "JDI Event Control Thread"s are still running, looks like an issue of JDI, not NetBeans.

All the remaining instances of JPDADebuggerImpl are held by the CompoundModel.
I've found out that this was actually already fixed in 8.0 by
http://hg.netbeans.org/core-main/rev/ef174ad3ab26
Comment 3 Martin Entlicher 2014-04-11 18:30:42 UTC
*** Bug 243146 has been marked as a duplicate of this bug. ***