Community
Participate
Working Groups
Eclipse has been crashing with varying levels of frequency for some time. Sometimes I can get several hours of work in before a crash, sometimes only a few minutes. There does not appear to be any particular action associated with the crash... sometimes simply moving the mouse will cause it. Eclipse does not leave a crash log file in the directory pointed to by the "user.dir" property as is often the case, I gather, so I cannot attach it to the bug. I get two message boxes, the first of which is a general windows one titled 'javaw.exe - Application Error' saying 'The instruction at "0xsomeaddress" references memory at "0xsomeotheraddress". The memory could not be "read".' I also get one titled 'Eclipse' with various pieces of information including an exit code of -1073741819 (not sure if it's the same every time, I'm just transcribing a screenshot that I created at one point) and exitdata of ea4_68, whatever that means. I can upload screenshots of either message box if that'll help. java -version reports: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) I had been running Eclipse 3.1 up until today, when I decided to upgrade to 3.1.1 to see if that fixed it. Sadly, it hasn't made any difference. I upgraded following the process outlined here: http://www.eclipse.org/eclipse/platform-releng/updatesfor3.1.1.html . OS is Windows XP SP1, so it's not the bug that was causing crashes under SP2 (which was fixed in 3.1.1 anyway I think). 1GB of physical memory. I have tried upping the maximum heap space by editing eclipse.ini, but it hasn't made any difference, and anyway the crashes sometimes occur very soon after starting eclipse when it would be very unlikely to have hit the upper bound yet. I even ran memtest86+ on my machine in case it was a faulty hardware problem, but that didn't reveal any hardware errors. No other applications crash on me like eclipse does anyway. This is driving me nuts, I'm willing to do any testing required to help in getting it diagnosed/fixed. :) I'll upload the output of running "java -verbose:jni -Xmx512M -Xcheck:jni -jar startup.jar" once the bug has been saved. It seems to be the only remotely useful output that I can get to upload, given the lack of crash dump and that the workspace .metadata/.log doesn't report anything useful. (Since bugzilla forces me to guess a component, I'll try SWT as the most likely candidate for a JVM crash since it's JNI heavy). Cheers Tom
Created attachment 33575 [details] Output from running java -verbose:jni -Xmx512M -Xcheck:jni -jar startup.jar
Oh, that log was from relatively short-lived session which crashed.
Are you still seeing this on 3.2 M6?
Hi Steve. I'll give that build a try today. Thanks for the followup.
Wow. Lots of time has gone by. Are you still crashing in Eclipse 3.2?
I have a lot of crashes on eclipse Europa in random actions. Eclipse hangs and the CPU is at 100% then I must to kill the process.
Please run Eclipse 3.4. When it crashes, attach the crash log. If you have no crash log, attach a screen shot. Also, try a different JVM to see whether that makes things better.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
