Bug 578557

Summary: "com.sun.jdi.ObjectCollectedException occurred while retrieving value" in Expressions view
Product: [Eclipse Project] JDT Reporter: Jörg Kubitz <jkubitz-eclipse>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: sarika.sinha
Version: 4.23   
Target Milestone: ---   
Hardware: All   
OS: All   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=537399
Whiteboard: stalebug
Attachments:
Description Flags
screenshot1
none
Screenshot 2: dealocated.png
none
Screenshot3 when expanding a node in the view none

Description Jörg Kubitz CLA 2022-02-03 07:25:43 EST 
Created attachment 287965 [details]
screenshot1

during debuging i sometimes i only see "com.sun.jdi.ObjectCollectedException occurred while retrieving value" or "dealocated" in Expressions view.

The expression contained array and stream processing.

Arrays.stream(trees).map(et->et.toString()).collect(Collectors.joining(""+(char)10))

Was already fixed for variables view in bug 537399
Comment 1 Jörg Kubitz CLA 2022-02-03 07:26:06 EST 
Created attachment 287966 [details]
Screenshot 2: dealocated.png
Comment 2 Jörg Kubitz CLA 2022-02-03 07:35:28 EST 
Created attachment 287967 [details]
Screenshot3 when expanding a node in the view

When expanding a node in the view the whole View sometimes goes berserk - not shown a list anymore (screenshot 3)
Comment 3 Sarika Sinha CLA 2022-05-25 02:46:37 EDT 
Same failure in tests:
https://download.eclipse.org/eclipse/downloads/drops4/I20220523-1800/testresults/html/org.eclipse.jdt.debug.tests_ep424I-unit-win32-java11_win32.win32.x86_64_11.html

testListLogicalStructure & 	testMapLogicalStructure


Error	com.sun.jdi.ObjectCollectedException occurred retrieving type

org.eclipse.debug.core.DebugException: com.sun.jdi.ObjectCollectedException occurred retrieving type
at org.eclipse.jdt.internal.debug.core.model.JDIDebugElement.throwDebugException(JDIDebugElement.java:263)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugElement.requestFailed(JDIDebugElement.java:202)
at org.eclipse.jdt.internal.debug.core.model.JDIDebugElement.targetRequestFailed(JDIDebugElement.java:182)
at org.eclipse.jdt.internal.debug.core.model.JDIValue.getUnderlyingType(JDIValue.java:459)
at org.eclipse.jdt.internal.debug.core.model.JDIValue.getJavaType(JDIValue.java:441)
at org.eclipse.jdt.debug.tests.variables.TestLogicalStructures.testListLogicalStructure(TestLogicalStructures.java:70)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at junit.framework.TestCase.runTest(TestCase.java:177)
at junit.framework.TestCase.runBare(TestCase.java:142)
at org.eclipse.jdt.debug.tests.AbstractDebugTest.runBare(AbstractDebugTest.java:2670)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:130)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at junit.framework.TestSuite.run(TestSuite.java:236)
at junit.framework.TestSuite.runTest(TestSuite.java:241)
at org.eclipse.jdt.debug.tests.DebugSuite$1.run(DebugSuite.java:61)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.sun.jdi.ObjectCollectedException
at org.eclipse.jdi.internal.MirrorImpl.defaultReplyErrorHandler(MirrorImpl.java:282)
at org.eclipse.jdi.internal.ObjectReferenceImpl.referenceType(ObjectReferenceImpl.java:531)
at org.eclipse.jdi.internal.ObjectReferenceImpl.type(ObjectReferenceImpl.java:548)
at org.eclipse.jdt.internal.debug.core.model.JDIValue.getUnderlyingType(JDIValue.java:457)
... 18 more
Comment 5 Eclipse Genie CLA 2024-05-20 02:32:44 EDT 
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.