Bug 129390

Created attachment 57871 [details]
stacktrace

The connection with the debugged application was lost. The application has finished or crashed or there was a network
problem. This exception does not have any negative impact. We would have to add a catch for VMDisconnectedException to
every JDI call to prevent from this. But that would likely reqiure a change of the threading of JDI calls, places where
we call JDI are spread accross the debuggerjpda module.

Build: NetBeans IDE Dev (Build 200804050004)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_04-b12
OS: Windows XP, 5.1, x86

User Comments: 
Stopped Debugging

Created attachment 60000 [details]
stacktrace

This issue has already 10 duplicates 

Created attachment 62454 [details]
stacktrace

*** Issue 136777 has been marked as a duplicate of this issue. ***

Additional comment:
When working with the new debugging view, this Exception is being thrown quite often (see issue 136777 for example)

Created attachment 62747 [details]
stacktrace

Created attachment 62875 [details]
stacktrace

Created attachment 62923 [details]
stacktrace

*** Issue 136883 has been marked as a duplicate of this issue. ***

Changing from P4 to P3 - it has a lot of duplicates.

*** Issue 137425 has been marked as a duplicate of this issue. ***

Known JDI issues that can affect this are:

VMDisconnectedException can wrongly be thrown if thread using JDI is interrupted
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6514055

JDI ThreadReference.frameCount() fails when thread is sleeping
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4783403

But now I get VMDisconnectedException from ThreadReferenceImpl.frameCount() called on a thread, which is suspended on a
breakpoint! I can continue stepping in it and get a new VMDisconnectedException after a step. The exception can not mean
that the debugger was disconnected from the debuggee here.

*** Issue 136628 has been marked as a duplicate of this issue. ***

I'm able to 100% reproduce this using steps from http://www.netbeans.org/issues/show_bug.cgi?id=136777.
It looks like there has appeared some thread from the first debugging session, which is already disconnected. Therefore
the VMDisconnectedException.

The attached cases hopefully fixed in trunk:
http://hg.netbeans.org/main/rev/3572328a4ec7
http://hg.netbeans.org/main/rev/398ba5619fb3

Integrated into 'main-golden', available in NB_Trunk_Production #268 build
Changeset: http://hg.netbeans.org/main/rev/3572328a4ec7
User: mentlicher@netbeans.org
Log: #129390 - Destroy the old nodes when a new root context is set.
This prevents from leaking the nodes and models and also fixes VMDisconnectedException that was thrown from leaked objects.

*** Issue 137735 has been marked as a duplicate of this issue. ***

Still reproducible by steps in issue 136777 in (Build 200806230002)

Created attachment 63382 [details]
stacktrace

*** Issue 138601 has been marked as a duplicate of this issue. ***

Created attachment 63844 [details]
stacktrace

Fixed.
changeset 157c86db6cbc in main
details: http://hg.netbeans.org/main?cmd=changeset;node=157c86db6cbc

Integrated into 'main-golden', available in NB_Trunk_Production #298 build
Changeset: http://hg.netbeans.org/main/rev/157c86db6cbc
User: Daniel Prusa <dprusa@netbeans.org>
Log: #129390: com.sun.jdi.VMDisconnectedException fixed

i found that this bug is exist in Netbeans 6.5 too.

Build: NetBeans IDE Dev (Build 200807040101)
OS: Ubuntu linux

reported in Exception 3176 by me (azizi)

Build: NetBeans IDE Dev (Build 200807170007)
VM: Java HotSpot(TM) Client VM, 11.0-b12, Java(TM) SE Runtime Environment, 1.6.0_10-beta-b25
OS: Windows Vista, 6.0, x86

User Comments: 
Clicked on Stop Debug of MIDP Application and then clicked manual GC icon

Created attachment 65027 [details]
stacktrace

Build: NetBeans IDE Dev (Build 200807221016)
VM: Java HotSpot(TM) Client VM, 1.5.0_13-121, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_13-b05-241
OS: Mac OS X, 10.4.11, i386

User Comments: 

Created attachment 65346 [details]
stacktrace

Build: NetBeans IDE Dev (Build 200807221016)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13
OS: Windows XP, 5.1, x86

User Comments: 


Stacktrace: 
com.sun.jdi.VMDisconnectedException
        at com.sun.tools.jdi.TargetVM.waitForReply(TargetVM.java:285)
        at com.sun.tools.jdi.VirtualMachineImpl.waitForTargetReply(VirtualMachineImpl.java:1015)
        at com.sun.tools.jdi.PacketStream.waitForReply(PacketStream.java:51)
        at com.sun.tools.jdi.JDWP$ThreadGroupReference$Children.waitForReply(JDWP.java:5903)
        at com.sun.tools.jdi.JDWP$ThreadGroupReference$Children.process(JDWP.java:5884)
        at com.sun.tools.jdi.ThreadGroupReferenceImpl.kids(ThreadGroupReferenceImpl.java:107)

Build: NetBeans IDE Dev (Build 200807221016)
VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13
OS: Windows XP, 5.1, x86

User Comments: 


Stacktrace: 
com.sun.jdi.VMDisconnectedException

Created attachment 65540 [details]
stacktrace

Build: NetBeans IDE Dev (Build 200807221016)
VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Linux, 2.6.24-20-generic, i386

User Comments: 


Stacktrace: 
com.sun.jdi.VMDisconnectedException: connection is closed
        at com.sun.tools.jdi.TargetVM.send(TargetVM.java:274)
        at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1011)
        at com.sun.tools.jdi.PacketStream.send(PacketStream.java:41)
        at com.sun.tools.jdi.JDWP$ThreadReference$FrameCount.enqueueCommand(JDWP.java:5300)
        at com.sun.tools.jdi.JDWP$ThreadReference$FrameCount.process(JDWP.java:5286)
        at com.sun.tools.jdi.ThreadReferenceImpl.frameCount(ThreadReferenceImpl.java:254)

Created attachment 65589 [details]
stacktrace

Again for 6.5... updated the TM.

Build: NetBeans IDE Dev (Build 200807040101)
VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Windows XP, 5.1, x86

User Comments: 
Tried to debug

Stacktrace: 
com.sun.jdi.VMDisconnectedException: connection is closed
        at com.sun.tools.jdi.TargetVM.send(TargetVM.java:274)
        at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1011)
        at com.sun.tools.jdi.PacketStream.send(PacketStream.java:41)
        at com.sun.tools.jdi.JDWP$EventRequest$Set.enqueueCommand(JDWP.java:6765)
        at com.sun.tools.jdi.JDWP$EventRequest$Set.process(JDWP.java:6735)
        at com.sun.tools.jdi.EventRequestManagerImpl$EventRequestImpl.set(EventRequestManagerImpl.java:179)

Created attachment 65728 [details]
stacktrace

More than 50 duplicates reported for builds after 20080704

Many duplicates. Should be fixed.

Nearly all reported VMDisconnectedExceptions fixed. It remains to investigate two more thrown at the following methods:

..jpda.JPDADebuggerImpl.initGenericsSupport(JPDADebuggerImpl.java:1259)
..jpda.ui.CurrentThreadAnnotationListener$AllThreadsAnnotator.<init>(CurrentThreadAnnotationListener.java:381)

Additional fixes:
changeset 1ffb242fe33b in main
details: http://hg.netbeans.org/main?cmd=changeset;node=1ffb242fe33b
changeset bd6d1aa3cbea in main
details: http://hg.netbeans.org/main?cmd=changeset;node=bd6d1aa3cbea

Build: NetBeans IDE Dev (Build 200807281401)
VM: Java HotSpot(TM) Client VM, 10.0-b22, Java(TM) SE Runtime Environment, 1.6.0_06-b02
OS: Windows XP, 5.1, x86

User Comments: 


Stacktrace: 
com.sun.jdi.VMDisconnectedException: Connection closed
        at com.sun.tools.jdi.TargetVM.send(TargetVM.java:274)
        at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1011)
        at com.sun.tools.jdi.PacketStream.send(PacketStream.java:41)
        at com.sun.tools.jdi.JDWP$ThreadGroupReference$Name.enqueueCommand(JDWP.java:5790)
        at com.sun.tools.jdi.JDWP$ThreadGroupReference$Name.process(JDWP.java:5776)
        at com.sun.tools.jdi.ThreadGroupReferenceImpl.name(ThreadGroupReferenceImpl.java:45)

Created attachment 66003 [details]
stacktrace

Integrated into 'main-golden', available in build *200807300201* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/1ffb242fe33b
User: Daniel Prusa <dprusa@netbeans.org>
Log: #129390: VMDisconnectedException fixed

Hi Daniel, what's about the 2 remaining throwns? Are they also fixed in build *200807300201*

Especially: Is fix for http://statistics.netbeans.org/analytics/detail.do?id=82475 included?

Hi, the remaining occurrences of the exception have not been fixed yet. I plan to do it by this Friday.

Fixed.
changeset d6fa3c076e35 in main
details: http://hg.netbeans.org/main?cmd=changeset;node=d6fa3c076e35

Integrated into 'main-golden', available in build *200807311401* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/d6fa3c076e35
User: Daniel Prusa <dprusa@netbeans.org>
Log: #129390, 141255, 142363: VMDisconnectedException, InvalidStackFrameException and InvocationTargetException fixed

Product Version: NetBeans IDE Dev (Build 200809061401)
Java: 1.6.0_10-rc; Java HotSpot(TM) Client VM 11.0-b15
System: Windows XP version 5.1 running on x86; Cp1250; cs_CZ (nb)

Verified. I have not encountered this Exception any more.

Reopening - reproduced in NetBeans IDE Dev (Build 200810171401)
http://statistics.netbeans.org/exceptions/detail.do?id=130190

We have fixed ObjectCollectedException in almost all  potential places, this is the first report since the date the
issue was closed. Now, the exception comes from AbstractObjectVariable.getClassType(). This should not occur frequently.
Decreasing priority to P3. 

changeset d43e7c85cd00 in main
details: http://hg.netbeans.org/main?cmd=changeset;node=d43e7c85cd00

Integrated into 'main-golden', will be available in build *200810220201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/d43e7c85cd00
User: Daniel Prusa <dprusa@netbeans.org>
Log: #129390: VMDisconnectedException fixed.

Reopening - reproduced in NetBeans IDE Dev (Build 200811130201)
http://statistics.netbeans.org/exceptions/detail.do?id=139165

Build: NetBeans IDE Dev (Build 200811130201)
VM: Java HotSpot(TM) Client VM, 1.5.0_16-133, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_16-b06-284
OS: Mac OS X, 10.5.5, i386

User Comments: 


Stacktrace: 
com.sun.jdi.VMDisconnectedException: connection is closed
        at com.sun.tools.jdi.TargetVM.send(TargetVM.java:274)
        at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:934)
        at com.sun.tools.jdi.PacketStream.send(PacketStream.java:41)
        at com.sun.tools.jdi.JDWP$VirtualMachine$Version.enqueueCommand(JDWP.java:34)
        at com.sun.tools.jdi.JDWP$VirtualMachine$Version.process(JDWP.java:25)
        at com.sun.tools.jdi.VirtualMachineImpl.versionInfo(VirtualMachineImpl.java:531)

Created attachment 73730 [details]
stacktrace

The VMDisconnectedException can be thrown on many places, it needs to be caught more centrally...
See issue #137310.

This should be finally fixed everywhere after issue #137310 was fixed.

Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.