Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323139 - JVM crash immediately upon Eclipse startup
Summary: JVM crash immediately upon Eclipse startup
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-19 09:22 EDT by Matt Brown CLA
Modified: 2011-01-31 16:07 EST (History)
2 users (show)

See Also:

Attachments
HotSpot crash dump (12.22 KB, text/plain)
2010-08-19 09:23 EDT, Matt Brown CLA 		no flags Details
Another HotSpot crash report (12.22 KB, text/plain)
2010-08-19 09:23 EDT, Matt Brown 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 Matt Brown CLA 2010-08-19 09:22:37 EDT 
Build Identifier: Eclipse IDE for Java Developers

When launching Eclipse, either through a shortcut or by calling eclipse.exe directly, the splash screen is displayed and then within a few seconds closes and the process terminates. It appears that HotSpot is crashing with a EXCEPTION_ACCESS_VIOLATION. I've attached a sample hs_err_pid log file from the eclipse installation directory.

Helios was working fine initially for me, and I do not recall what actions I took prior to the crashes beginning.

The crash occurs if Eclipse is run in the JRE or if I add a --vm argument to eclipse.ini to point to a JDK. A separate Galileo installation on the same machine runs without problem.

Reproducible: Always

Steps to Reproduce:
1. Attempt to run Eclipse
Comment 1 Matt Brown CLA 2010-08-19 09:23:14 EDT 
Created attachment 176990 [details]
HotSpot crash dump
Comment 2 Matt Brown CLA 2010-08-19 09:23:31 EDT 
Created attachment 176991 [details]
Another HotSpot crash report
Comment 3 Remy Suen CLA 2010-08-19 18:22:36 EDT 
This looks more like a problem with the VM than with Eclipse.
Comment 4 John Arthorne CLA 2010-08-20 10:42:54 EDT 
(In reply to comment #3)
> This looks more like a problem with the VM than with Eclipse.

I agree, the error occurs in a native called by the java.util.jar.JarVerifier. The crash file contains information on how to report the problem to the VM vendor.