Summary: | Variables view: 'All Instances' shows garbage collected instances | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | curtis.windatt.public, darin.eclipse, Michael_Rennie, stephan.herrmann |
Version: | 3.6 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: | stalebug |
Description
Dani Megert
2009-09-16 05:21:29 EDT
VM: java version "1.6.0_16" Java(TM) SE Runtime Environment (build 1.6.0_16-b01) Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode) AFAIK we query the vm for all instances and display them to the user. We don't cache them or do much with them at all. I would imagine this is a VM bug. Investigate in M3. There does appear to be some debugger interaction here... if I just use the "Run As > JUnit Test" shortcut without using a breakpoint, the number of instances in memory does *not* grow. As soon as I use a breakpoint in TestRoot, the instances start to grow. When I use an IBM VM, instances do grow after hitting a breakpoint. However, using the GC button reduces the instances to 1. *** Bug 287852 has been marked as a duplicate of this bug. *** Bug 287852 comment#6 mentions this VM bug: http://bugs.sun.com/view_bug.do?bug_id=4858370 adding it here for reference. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |