Bug 139166 - Eclipse JVM Exit, exitdata = 55c_3c
Summary: Eclipse JVM Exit, exitdata = 55c_3c
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.1.2   Edit
Hardware: PC Windows 2000
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2006-04-28 10:17 EDT by Isaac Shabtay CLA
Modified: 2006-04-28 11:12 EDT (History)
0 users

See Also:

Attachments
JVM error log (9.19 KB, text/plain)
2006-04-28 11:05 EDT, Isaac Shabtay CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Shabtay CLA 2006-04-28 10:17:18 EDT 
The entire platform crashes with exitdata 55c_3c. Nothing in Eclipse's log files.
See attachment for a shot of the exit window.

Eclipse log *after* restarting shows:

--- Begin log ---
!SESSION 2006-04-28 10:11:19.659 -----------------------------------------------
eclipse.buildId=M20060118-1600
java.version=1.4.2_10
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2006-04-28 10:11:27.500
!MESSAGE A workspace crash was detected. The previous session did not exit normally.
--- End log ---
Comment 1 Pascal Rapicault CLA 2006-04-28 10:21:03 EDT 
Do you have a vm log?
Comment 2 Isaac Shabtay CLA 2006-04-28 10:25:22 EDT 
No I don't. Can it be found anywhere in the workspace's directories? I'm not too familiar with the various Eclipse loggers.
Comment 3 John Arthorne CLA 2006-04-28 11:02:58 EDT 
If there is a VM crash, there should be a file in the working directory that you launched from (typically the "eclipse" directory).  Depending on the VM, it may be called "javacore<date>" or "hs_error_<pid>" Where <date> is the date of the crash, or <pid> is the process id of the java process.
Comment 4 Isaac Shabtay CLA 2006-04-28 11:05:59 EDT 
Created attachment 39780 [details]
JVM error log
Comment 5 John Arthorne CLA 2006-04-28 11:10:39 EDT 
Thanks for the dump file.  This is clearly a VM bug - the error occurs in a thread called "VMThread", and the error is in a VM DLL; there is no further stack details to go on.  If this is consistently reproduceible for you then I suggest reporting it to the VM provider.
Comment 6 Isaac Shabtay CLA 2006-04-28 11:12:57 EDT 
No problem. I'll report it to Sun.
Thank you!