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.
The 6.9.1 ID quite often dies when I edit dialogs. In this can a dump,is written (unfortunatly 200MByte) as well as the logfiles. I can only attach the logfiles thus. I have saved the dump. If you need it, tell me where to upload it to Note that my PC is a i7 with 8GBytes of RAM running Ubuntu 10.04 and a SUN JDK 1.6.0_20
Created attachment 104531 [details] logs / uigestures. dump can be send additionally (50MBytes zipped)
Often happens when customizing a GridBagLayout with manually prior cloned entities. As well this happened after having cloned a complete Panel by Copy from one dialog and paste into the new one.
This starts to get really tiring. It happens FAR too often! Had at least 10 dead NBs in the last 20 minutes and always lost what was not saved explicitly before. I have the impression that it happens often when using the resource editor !
So what exactly happens when NB dies? Is it frozen on a deadlock, or is it a JVM crash (the application just disappears)? In case of a freeze we need a thread dump, see http://wiki.netbeans.org/GenerateThreadDump. In case of JVM crash there should be a hs_err_pid<pid>.log file somewhere (most probably in the installation directory under 'bin' folder). It's most likely a JDK bug in such case. The dump of 200MB you mention is probably a memory dump - would make sense if you faced a OutOfMemoryError, but that does not seem to be the case. The NB log files you attached do not contain anything special.
On Linux the hs_err_pid* file should actually appear in current working directory. You can also specify the path when starting NetBeans like: ./netbeans -J-XX:ErrorFile=path_to_log_file
The application just disappears ! I have changed the startup parameters to find a log file next time. I will attach to this bug once I have one.
Closing for now, until we have the error logs.
Created attachment 105495 [details] Another logfiles from /var/log (nothing else found)
Tried to follow you hint to configure an error-log but not successfull. Neither the appending of -J-XX:ErrorFile=path_to_log_file to the starter as well as into the netbeans.conf file. Have attached what I have found in the var/log folder though again.
Strange you get no log file. Please make sure you enter valid path, including file name that should be created. Best to run from terminal like: netbeans -J-XX:ErrorFile=./hs_err_pid.log Also when running from terminal it should print at least something to console when JVM crashes. See also bug 187176.
Got an error message just before in the console where I start from now. Here it is ... <SNIP> sc1@schome-i7:~$ ./start_nb.rc 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 215173 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.) </SNIP> It happened again using the gridbaglayut editor after haveing copied a panel. After placeing the panel correctly I just wanted to close the dialog and got this problem. Will now launch with the --sync option as stated in the short bug message.
Just started a NB Project inside the IDE for debuggin and got an XWindow Exception. Find it attached.
Created attachment 105958 [details] BUg Trace
Get that message now always (since --sync is on). xserver : 1.7.5+5unbunut1
(In reply to comment #12) > Just started a NB Project inside the IDE for debuggin and got an XWindow > Exception. > > Find it attached. The attached exception is from NetBeans, not from X Window (which is native system we don't call from Java, so much likely some JVM problem). Anyway, you can test easily if there is some relation of this exception to the crashes. On the stacktrace there is some 'jgesic' module which does not seem to be a standard NB module. Can you uninstall it? Or better, try running NB with clear settings (an empty userdir)? See http://wiki.netbeans.org/FaqAlternateUserdir
This is not a stopper for NB 7.0 Beta 2, still track as high-priority issue, that should be resolved by NB 7.0 FCS.
Need more info. Please, see comment #15 above. Closing INCOMPLETE for now.