StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would post this as a comment but I don't have enough rep. First of all can you tell us the version of windows you are running? 98/2000/XP/Vista/7/8? </p> <p>Take your application to another computer (with the same OS) and see if it crashes too. If yes try another OS from a different family (linux/mac). If the problem is isolated to a particular family of OS then the problem might be dependent to a particular method call in your program. If its just your computer then it becomes much harder to debug. If this problem happens to all OS families then suspect a JVM bug.</p> <p>If your using Windows Vista/7, try turning off UAC. Something about your user profile privileges might be blocking java from accessing a critical library (from the error dump User32.dll?). If this does solve you problems, once again experiment on yours and another computer with different UAC levels and check if the problem is isolated to a particular machine/UAC level.</p> <p>Monitor both your system memory and your heap size during application startup, it may just be that your application actually filled out all the available RAM that the JVM didn't have memory to produce a hs_error_* file (this has happen to me before).</p> <p>If all else fails, I recommend using a debugger to determine where the application fails. Maybe stick a System.exit(0); at different parts of your program to see if it executes to that part before crashing. Also determine if the crash is predictable (i.e fails at the same point vs randomly failing). A predictable crash suggests something in the code triggering the crash. If you are using JNI, temporarily disable them with dummy methods to see if the crash still happens.</p> <p>Thats all I can really say... It can be a billion reasons, hope you find the one.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload