Bug 81303 - Eclipse JVM crashes when checking out from CVS
Summary: Eclipse JVM crashes when checking out from CVS
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.1   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2004-12-15 15:23 EST by Veronika Irvine CLA
Modified: 2005-01-06 08:46 EST (History)
1 user (show)

See Also:

Attachments
JVM crash file (15.01 KB, text/plain)
2004-12-15 15:25 EST, Veronika Irvine CLA 		no flags Details
javanativecrash.log (15.01 KB, text/plain)
2004-12-15 15:27 EST, Veronika Irvine 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 Veronika Irvine CLA 2004-12-15 15:23:35 EST 
eclipse.buildId=I20041214-2000
java.version=1.4.2_05
java.vendor=Apple Computer, Inc.
BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US
Framework arguments:  -keyring /Users/vikki/.eclipse_keyring -showlocation
Command-line arguments:  -os macosx -ws carbon -arch ppc -keyring /Users/vikki/.eclipse_keyring 
-consoleLog -showlocation

I was checking a project out of eclipse.org as anonymous@pserver when eclipse crashed.  Here is all I 
could find:

!ENTRY org.eclipse.osgi 2004-12-15 14:50:46.428
!MESSAGE While loading class "org.eclipse.jdt.core.JavaCore$7", thread "Worker-4" timed out waiting 
(5000ms) for thread "Worker-2" to finish starting bundle "org.eclipse.jdt.core". To avoid deadlock, 
thread "Worker-4" is proceeding but "org.eclipse.jdt.core.JavaCore$7" may not be fully initialized.
!STACK 0
java.lang.Exception: Generated exception.
	at org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:
102)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:371)
	at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
	at 
org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:93)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
	at org.eclipse.jdt.core.JavaCore$6.run(JavaCore.java:4125)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Comment 1 Veronika Irvine CLA 2004-12-15 15:25:35 EST 
Created attachment 16673 [details]
JVM crash file

Found JVM crash file
Comment 2 Pascal Rapicault CLA 2004-12-15 15:26:49 EST 
Don't you have more info?
The stack info seems to be unrelated to the problem.
Comment 3 Veronika Irvine CLA 2004-12-15 15:27:17 EST 
Created attachment 16674 [details]
javanativecrash.log
Comment 4 Michael Valenta CLA 2004-12-15 15:58:04 EST 
I don't see CVS anywhere in the crash trace. Moving back to Runtime.
Comment 5 John Arthorne CLA 2004-12-16 10:54:20 EST 
Looks like a VM bug.  Was it reproducible?
Comment 6 Veronika Irvine CLA 2004-12-16 11:13:01 EST 
I only saw it once.  Haven't had much chance to try to recreate it 
consistantly.
Comment 7 Pascal Rapicault CLA 2005-01-06 08:46:57 EST 
Reopen I you see it again.