Bug 22309 - com.sun.jdi.ObjectCollectedException
Summary: com.sun.jdi.ObjectCollectedException
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Darin Wright CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-09 11:38 EDT by Genady Beryozkin CLA
Modified: 2019-01-09 13:43 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Genady Beryozkin CLA 2002-08-09 11:38:49 EDT
I get it in the log file with 1.4.1beta.
I use the jdt-core patch posted on the website.

Genady

!ENTRY org.eclipse.jdt.debug 4 5010 аев 09, 2002 18:27:27.764
!MESSAGE com.sun.jdi.ObjectCollectedException occurred while retrieving value.
!STACK 0
com.sun.jdi.ObjectCollectedException
	at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler
(MirrorImpl.java:235)
	at org.eclipse.jdi.internal.ArrayReferenceImpl.getValues
(ArrayReferenceImpl.java:95)
	at org.eclipse.jdi.internal.ArrayReferenceImpl.getValue
(ArrayReferenceImpl.java:56)
	at 
org.eclipse.jdt.internal.debug.core.model.JDIArrayEntryVariable.retrieveValue
(JDIArrayEntryVariable.java:56)
	at 
org.eclipse.jdt.internal.debug.core.model.JDIVariable.getCurrentValue
(JDIVariable.java:61)
	at org.eclipse.jdt.internal.debug.core.model.JDIVariable.getValue
(JDIVariable.java:83)
	at 
org.eclipse.debug.internal.ui.views.variables.VariablesView.populateDetailPaneF
romSelection(VariablesView.java:640)
	at 
org.eclipse.debug.internal.ui.views.variables.VariablesView$5.selectionChanged
(VariablesView.java:622)
	at org.eclipse.jface.viewers.Viewer.fireSelectionChanged
(Viewer.java:147)
	at org.eclipse.jface.viewers.StructuredViewer.updateSelection
(StructuredViewer.java:1155)
	at org.eclipse.jface.viewers.StructuredViewer.handleSelect
(StructuredViewer.java:544)
	at org.eclipse.jface.viewers.StructuredViewer$1.widgetSelected
(StructuredViewer.java:568)
	at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent
(OpenStrategy.java:171)
	at org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:168)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent
(OpenStrategy.java:297)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1529)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1291)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1177)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:1160)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:775)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:248)
	at org.eclipse.core.launcher.Main.run(Main.java:698)
	at org.eclipse.core.launcher.Main.main(Main.java:534)
Comment 1 Joe Szurszewski CLA 2002-08-12 12:41:07 EDT
Genady, can you give some details on what you were doing when this occurred?  Do you have a 
reproduceable test case?
Comment 2 Genady Beryozkin CLA 2002-08-12 12:53:28 EDT
I was debugging an application and "inspected" an expression I evaluated
in the display view.
Comment 3 Jared Burns CLA 2002-08-14 10:28:15 EDT
I think we'll need a reproducible test case to do anything about this. Without 
a test case, it just looks like an exception occurred and we handled it.
Comment 4 Darin Wright CLA 2002-08-14 10:46:12 EDT
It looks like the inspected object was garbage collected on the target VM, 
before we tried to render its details. It looks like the debugger handled the 
condition, and logged the exception - but I do not think there is a debugger 
bug here. Marking as "invalid", unless we can find a repoduceable test case.