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.
This bug was originally marked as duplicate of bug 199510, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 7.2 (Build 201206291011) VM: Java HotSpot(TM) Client VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b05 OS: Windows XP User Comments: mps77: suspend debugger on breakpoint hit. edit code. save file. stop debugger. crash. :) softwarevisualization: ended forgotten debugging session Stacktrace: com.sun.jdi.VMDisconnectedException: Connection closed at com.sun.tools.jdi.TargetVM.send(TargetVM.java:293) at com.sun.tools.jdi.VirtualMachineImpl.sendToTarget(VirtualMachineImpl.java:1032) at com.sun.tools.jdi.PacketStream.send(PacketStream.java:59) at com.sun.tools.jdi.JDWP$ReferenceType$MethodsWithGeneric.enqueueCommand(JDWP.java:2814) at com.sun.tools.jdi.JDWP$ReferenceType$MethodsWithGeneric.process(JDWP.java:2800) at com.sun.tools.jdi.ReferenceTypeImpl.methods(ReferenceTypeImpl.java:461)
Created attachment 121993 [details] stacktrace
Product Version: NetBeans IDE 7.2 (Build 201207092359) Java: 1.7.0_05; Java HotSpot(TM) Client VM 23.1-b03 System: Linux version 3.0.0-12-generic running on i386; UTF-8; cs_CZ (nb) User directory: /home/cesilko/.netbeans/7.2 Cache directory: /home/cesilko/.cache/netbeans/7.2 I couldn't reproduce the crash in 7.2 FCS candidate. I toggled line 3 breakpoint and pressed Ctrl+F5 to start debugging session. When the breakpoint was hit I invoked "Debug > Pause" from main menu. I changed "Hello" to "Hi" at line 3 and pressed Ctrl+S. Pressing Shift+F5 correctly stopped the application and NetBeans didn't crash. 01 public class JavaApplication4 { 02 public static void main(String[] args) { 03 System.out.println("Hello world."); 04 } 05 }
This is nothing serious, an exception does not necessarily mean a crash. It's unfortunate, that LocationImpl.equals() sends something through the net and throws exceptions.
I do not think this is reproducible, there needs to be specific timing of the actions for this bug to occur. I can be fixed only by eliminating LocationImpl.equals() call.
Created attachment 124868 [details] stacktrace Debugging java project
Fixed by changeset: 235106:32f448eb6f72 http://hg.netbeans.org/main/rev/32f448eb6f72
Integrated into 'main-golden', will be available in build *201210060002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/32f448eb6f72 User: mentlicher@netbeans.org Log: #215493: Catch VMDisconnectedException.