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.
Steps: MemoryView test application. 1. start debugging 2. stop on a breakpoint 3. open threads view 4. invoke Continue action - the application should run in debug mode without stopping The exception is thrown periodically. It is hard to stop debugger or close Threads view because the exception dialog is modal and after closing of one another is opened. com.sun.jdi.InternalException: Unexpected JDWP Error: 13 at com.sun.tools.jdi.JDWPException.toJDIException(JDWPException.java:47) at com.sun.tools.jdi.ThreadReferenceImpl.currentContendedMonitor(ThreadReferenceImpl.java:433) at org.netbeans.modules.debugger.jpda.models.JPDAThreadImpl.getContendedMonitor(JPDAThreadImpl.java:392) at org.netbeans.modules.debugger.jpda.ui.models.MonitorModel.getChildren(MonitorModel.java:107) at org.netbeans.spi.viewmodel.Models$CompoundTreeModel.getChildren(Models.java:590) at org.netbeans.spi.viewmodel.Models$CompoundModel.getChildren(Models.java:2208) [catch] at org.netbeans.modules.viewmodel.TreeModelNode$TreeModelChildren.evaluateLazily(TreeModelNode.java:522) at org.netbeans.modules.viewmodel.TreeModelNode$LazyEvaluator.run(TreeModelNode.java:907)
This is a part of a more complex problem described in issue #96519. I plan to create a "masking" fix specifically for 5.5.1 release, since the complex fix of issue #96519 is too risky. Thus we will just silently catch com.sun.jdi.InternalException, similar to other exceptions which we already catch there.
Created attachment 39549 [details] The proposed fix. Silently ignore the strange exception like others.
This is a bug in JDI. Proposed solution is the only way NB debugger can work-around it, the fix is safe enough for integration into NB 5.5.1.
Fixed in release551: /shared/data/ccvs/repository/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/JPDAThreadImpl.java,v <-- JPDAThreadImpl.java new revision: 1.13.2.1.2.1.22.1; previous revision: 1.13.2.1.2.1
Continue with steps: 5. toggle breakpoint somewhere and let debugger to stop 6. invoke step over Result: there is some timeout which blocks debugger for about 10 seconds, threads view contains 'Please wait...' in this time. Is it possible to do something with it? But timeout is definitely better than endless exceptions :).
Verified.