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.
Product Version: NetBeans IDE 6.8 Beta (Build 200910171337) Java: 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01 System: Linux version 2.6.31-14-generic running on amd64; UTF-8; en_US (nb) I was trying to reproduce this issue: http://www.netbeans.org/issues/show_bug.cgi?id=175016 Using the following steps I made the ide crash. 1) Open a java project and a java file 2) Clone the opened document 3) Now in the cloned window breakpoints cannot be added (clicking on gutter won't work, option in popup menu is disabled) 4) Go to the cloned window 5) Invoke Debug-> New Breakpoint or press Ctrl+F8 6) Select Line breakpoint from the combo box 7) Press ok 8) Netbeans crash I cannot reproduce the crash always (and with no success yet with a clean userdir). It usually takes a bit of playing around (cloning multiple times, docking elsewhere in the IDE). There was no message in the logfile, only the following message in the console: The program '<unknown>' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 10911 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Not sure where to assign this, but since it occurs while adding a breakpoint I'm putting it to debugger. I'll add more reliable steps to reproduce if I succeed in finding some.
Product Version: NetBeans IDE 6.8 Beta (Build 200910202101) Java: 1.6.0_16; Java HotSpot(TM) 64-Bit Server VM 14.2-b01 System: Linux version 2.6.31-14-generic running on amd64; UTF-8; en_US (nb) Now the crash occurred when adding a watch after confirming the New Watch dialog. I'm still not sure this is a debugger issue, please reassign as neccessary. Console output: The program '<unknown>' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 20526 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) As this happened several times in the last two days and I think it should be investigated before releasing beta -> raising to P1.
Is anything in messages log file? Can you please attach it here? Does it happen also with 32-bit JVM? From the message it looks like JVM/Swing problem. It has never happened to me, but will try the steps...
There was nothing suspicious to me in the log file, but I'll attach it. If there could have been, the JVM died before writing it to the file. There was nothing more than the error message on stdout. I've not yet tried to reproduce this on a 32bit JVM.
Created attachment 89857 [details] Messages log prior to the crash
I suggest this not be a beta stopper. This issue is random and there are no 100% reliable steps to reproduce AFAIK. I can not reproduce it on 32-bit JVM on Ubuntu linux 2.6.22-14. Tried both -client and -server. Vojto, both reported crashes are with -server, can you also try it with -client? I have a strong feeling that this is a JVM bug. See for instance: http://bugs.sun.com/view_bug.do?bug_id=6589541 http://bugs.sun.com/view_bug.do?bug_id=6848343 http://bugs.sun.com/view_bug.do?bug_id=6847604 Unfortunately, when I run NetBeans under gdb, I get crashes of JVM - Segmentation fault.
Threads are crashing with SIGSEGV, Segmentation fault under gdb, which makes native debugging impossible. Closing as wontfix - if the bug will be reproducible, please submit into bugtraq.
v/c