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.
I have attached another NetBeans instance remotely and as I choose Step Over I get the exception again and again. I was debugging org.netbeans.modules.refactoring.java.spi.JavaRefactoringPlugin.processFiles(Set<FileObject>,CancellableTask<WorkingCopy> ,ClasspathInfo) method. Product Version: NetBeans IDE Dev (Build 20080527050033) Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05 System: Linux version 2.6.22-14-generic running on i386; UTF-8; en_US (nb) STACKTRACE: (first 10 lines) com.sun.jdi.ObjectCollectedException at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:27) at com.sun.tools.jdi.ThreadReferenceImpl.jdwpStatus(ThreadReferenceImpl.java:191) at com.sun.tools.jdi.ThreadReferenceImpl.isSuspended(ThreadReferenceImpl.java:201) at org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl.<init>(JPDAThreadImpl.java:104) at org.netbeans.modules.debugger.jpda.models.ObjectTranslation.createTranslation(ObjectTranslation.java:102) at org.netbeans.modules.debugger.jpda.models.ObjectTranslation.translate(ObjectTranslation.java:172) at org.netbeans.modules.debugger.jpda.JPDADebuggerImpl.getThread(JPDADebuggerImpl.java:1290) at org.netbeans.modules.debugger.jpda.models.JPDAThreadGroupImpl.getThreads(JPDAThreadGroupImpl.java:89) at org.netbeans.modules.debugger.jpda.models.ThreadsTreeModel.computeChildren(ThreadsTreeModel.java:155) at org.netbeans.modules.debugger.jpda.models.ThreadsTreeModel.recomputeChildren(ThreadsTreeModel.java:177)
It seems to be reproducible even in NB 6.1 according to the first reporter (http://statistics.netbeans.org/exceptions/detail.do?id=45404).
Are there any steps to reproduce this? It looks like this is triggered by Threads View. The ThreadsCache seems to remember some threads which have already gone. Concrete steps to reproduce would help us to identify the problem.
Unfortunately it is random for me.
Since any method on ObjectReference can throw ObjectCollectedException, we should add catches for that exception to all such places. Scheduling for future, this is a fair amount of work.
This issue has already 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=45404
Created attachment 62541 [details] stacktrace
Created attachment 62628 [details] stacktrace
Product Version: NetBeans IDE Dev (Build 080609) Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06 System: SunOS version 5.11 running on x86; ISO646-US; en (nb) I was able to reproduce this exception repeatedly with the following steps TEST PROJECT: MemoryView 1 - Create new Watches for variables a, i, s, v 2 - Put caret on line 194 of MemoryView.java 3 - Invoke Run To Cursor action 4 - Again: Put caret on line 194 of MemoryView.java 5 - Again: Invoke Run To Cursor action ( = new session is created) 6 - Exception
Created attachment 62713 [details] stacktrace
This issue has already 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=45404
Created attachment 63108 [details] stacktrace
Created attachment 63140 [details] stacktrace
Created attachment 63188 [details] stacktrace
Created attachment 63401 [details] stacktrace
This issue has already 50 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=45404
*** Issue 139131 has been marked as a duplicate of this issue. ***
Fixed. changeset c265eaeab9d9 in main details: http://hg.netbeans.org/main?cmd=changeset;node=c265eaeab9d9
Integrated into 'main-golden', available in NB_Trunk_Production #324 build Changeset: http://hg.netbeans.org/main/rev/c265eaeab9d9 User: Daniel Prusa <dprusa@netbeans.org> Log: #135877: ObjectCollectedException fixed
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.