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.
Version used: Netbeans 6.8 Java SE from Netbeans.org OS: openSUSE 11.2 64-bit We are building a platform application on top of Netbeans 6.8, and as such we are using the Netbeans debugger regularly. We found that when we run our application in debugging mode, and put a breakpoint anywhere in our implementation code of the org.openide.nodes.node.Property class (specifically the setValue method) the Java process freezes, freezing Netbeans and the whole OS with it. Only killing the Java process in which the application that is being debugged works to unfreeze the system. I should note that the application works just fine out of debugger mode (no run time errors), this *only* occurs while in debugging mode.
This is very likely due to the native X grab lock. See issue #93076, there's a workaround: Have a look at http://wingware.com/doc/howtos/debug-x-grab Specifically, under (2): Setting option "AllowDeactivateGrabs" "true" in xorg.conf. *** This bug has been marked as a duplicate of bug 93076 ***
It seem plausible this bug is related to some X related problem, as I cannot reproduce the bug under Windows. However the suggested workaround does not seem to work either; I added the line in my /etc/X11/xorg.conf file under ServerOptions and restarted my X server. Then I took the steps to reproduce the bug. The magic key combination CTRL+ALT+\ (on the numpad) did not seem to do anything - am I using it incorrectly? The whole desktop environment (except for the mouse cursor) stays frozen. What *is* supposed to happen? So far the only robust method is killing the java process in which the debugger is running.
Have a look at http://bugs.sun.com/view_bug.do?bug_id=6517045 NetBeans will not help you with this, since this is out of their control. When the whole desktop environment stays frozen, your application is likely suspended while holding the mouse/keyboard grab. Therefore no other application can respond to mouse/keyboard events, including NetBeans. The solution (if the workaround does not work - I did not try it myself) is not to suspend your program at that point, or run it on a separate desktop.
verified duplicate