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.

Bug 178685 - debugger breakpoints in this method lock up the entire linux system
Summary: debugger breakpoints in this method lock up the entire linux system
Status: CLOSED DUPLICATE of bug 93076
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-15 15:05 UTC by pbowyer
Modified: 2010-05-06 08:02 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
An abridged class file that contains the method causing the problem (6.63 KB, text/plain)
2009-12-15 15:05 UTC, pbowyer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pbowyer 2009-12-15 15:05:34 UTC
Created attachment 92638 [details]
An abridged class file that contains the method causing the problem

The method "private void availableVodComboBoxActionPerformed(java.awt.event.ActionEvent evt)" in "public class ViewOriginDlgNew extends javax.swing.JDialog {}" locks up my entire PCLinuxOS system when I set a break point within the method. I've attached an abridged class file that contains this method and the other methods that access it.

With the break point set, the initialization code causes the debugger to pause within the above mentioned method, but it does not lock up the system at that time. After all of the initialization is done and I select an item in the Combo Box with a break point set in the offending method, the debugger breaks at the proper point, but I can no longer do anything with my system but push the reset button. The mouse pointer is still functioning, but mouse clicks and keyboard operations are useless. I cannot do anything to close the debugger or get access to the system to kill Netbeans.

This problem occurred in Netbeans 6.7 (and previous) also and I had worked around the problem by using "System.out.println()" calls to output the variables I was interested in so I could get the program running properly.

I recently received a message from "quality@netbeans.org" telling me that issue
"150135	IllegalStateException: Bad expression type: null"
had been addressed so I thought I'd try setting a break point in this offending method to see if it impacted the result I experienced previously, but I'm still experiencing system lockups when I do so. I'm uncertain if the aforementioned issue is related to this problem.
Comment 1 Martin Entlicher 2009-12-16 07:45:03 UTC
This problem is NetBeans-independent, it's caused by Java VM taking native XGrab lock. When your application is suspended while holding the XGrab, no other application can take focus and therefore the system looks like frozen. The resolution is only to kill the debugged app from the terminal.

This was already submitted as bug #93076. There's also a workaround - set option "AllowDeactivateGrabs" to "true" in xorg.conf.

*** This bug has been marked as a duplicate of bug 93076 ***
Comment 2 Marian Mirilovic 2010-05-06 08:02:51 UTC
verified duplicate