Created attachment 99799 [details]
messages.log from after crash

attaching messages.log

Could you please inspect for "hs_err_pid*" files (most probably they will exist in NB installation directory)?

Please attach the hotspot crash file. It's problem of your OS or JVM as the IDE has no native library and it's only managed code. Without the hs_err_pid file I am not able to report the issue to hs.
THanks

The exception at the log is unrelated it's issue #186321 which is already fixed in trunk.
In the issue there is also description how to workaround the issue.

(In reply to comment #2)
> Could you please inspect for "hs_err_pid*" files (most probably they will exist
> in NB installation directory)?

Unfortunately, there is no 'hs_err_pid*' file in either my netbeans installation or .netbeans directories.  Is there any other place or different type of filename where this could exist?  This problem happens fairly frequently, I'll look for this file again the next time it does.

On windows the hs_err_pid should be generated the current directory and if not successful, to the TEMP directory for the user.

(In reply to comment #6)
> On windows the hs_err_pid should be generated the current directory and if not
> successful, to the TEMP directory for the user.
I'm running Linux and I searched the entire drive for any file beginning with 'hs_' and there were none.  Any other ideas?

Sorry, I've overlooked the platform.
On linux it should go current working directory.
You can also use the jvm option -XX:ErrorFile=path_to_log_file.
You can pass it to NB by:
./netbeans -J-XX:ErrorFile=path_to_log_file

(In reply to comment #8)
> Sorry, I've overlooked the platform.
> On linux it should go current working directory.
> You can also use the jvm option -XX:ErrorFile=path_to_log_file.
> You can pass it to NB by:
> ./netbeans -J-XX:ErrorFile=path_to_log_file

I've experienced an IDE crash again.  This time while attempting to revert a file from a Mercurial repository.  Again, no hs_err*.log file was generated.  I've executed the command find . -iname 'hs_*' (from / as root).  I've even created a file hs_err_x.log file in the places where this file is expected to be generated to guarantee that the above command will find these files.  Any other ideas?

Try the -XX:ErrorFile option.
If it does not help, try at least to run the IDE from terminal, when hotspot crashes it prints at least some info to console.
Thanks

(In reply to comment #10)
> Try the -XX:ErrorFile option.
> If it does not help, try at least to run the IDE from terminal, when hotspot
> crashes it prints at least some info to console.
> Thanks

Finally!  Following is the output from running netbeans from the terminal after the error has occurred:

jdonmoyer@jdonmoyer-ubuntu:~/netbeans-6.9rc2/bin$ ./netbeans
Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future
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 122932 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 a clarification, this time it occurred after dismissing a dialog that was launched from within netbeans using ant's input capability from my freeform project build script:

<input message="Please specify a test case to run:" addproperty="case" />

The common thread in every occurrence where I've seen the IDE crash is that it always occurs after dismissing a netbeans launched dialog.

Let me know if I can assist in any other way with tracking this down.

Seems as a problem in JVM Window manager communication.
Do you use the standard Ubuntu window manager (compiz)?
Thanks

(In reply to comment #12)
> Seems as a problem in JVM Window manager communication.
> Do you use the standard Ubuntu window manager (compiz)?
> Thanks

Ubuntu 10.04 (same machine has been upgraded since about 8.04).  I use compiz, but have installed compiz settings manager in order to workaround some bugs (inconsistencies) in other apps that have been introduced since the switch to compiz.