Bug 235759 - [x86-64] Eclipse Crashes
Summary: [x86-64] Eclipse Crashes
Status: RESOLVED DUPLICATE of bug 214092
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.4   Edit
Hardware: PC Linux
: P3 blocker with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: vm
Depends on:
Blocks:
 
Reported: 2008-06-05 01:55 EDT by Mark Fortner CLA
Modified: 2008-06-19 09:42 EDT (History)
1 user (show)

See Also:


Attachments
When running only with Iced Tea (Java 7) (138.72 KB, application/octet-stream)
2008-06-05 01:55 EDT, Mark Fortner CLA
no flags Details
When running with Java 6 and Iced Tea (138.12 KB, application/octet-stream)
2008-06-05 01:56 EDT, Mark Fortner CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Fortner CLA 2008-06-05 01:55:35 EDT
Created attachment 103697 [details]
When running only with Iced Tea (Java 7)

Build ID: I20080523-0100

Steps To Reproduce:
1. Startup Eclipse
2. Wait a few seconds
3. Eclipse crashes


More information:
I'm running the x86-64 version of Ubuntu Hardy Heron.  I've installed the 64-bit version of Sun's VM.  The ~/.eclipse/eclipserc file has the following lines in it:
/usr/lib64/jvm/java-6-sun/bin/java
/usr/lib64/jvm/java-7-openjdk/bin/java

The enclosed log files should provide the rest of the configuration information including my permgen, memory and garbage collection settings.
Comment 1 Mark Fortner CLA 2008-06-05 01:56:24 EDT
Created attachment 103698 [details]
When running with Java 6 and Iced Tea
Comment 2 Mark Fortner CLA 2008-06-05 01:57:58 EDT
I've tried deleting and recreating my .workspace, and my .project files but that had no effect.

I've also tried running eclipse using -clean but also to no effect.
Comment 3 Remy Suen CLA 2008-06-05 08:17:31 EDT
Please see bug 214092 and its thousands of duplicates.
Comment 4 John Arthorne CLA 2008-06-19 09:42:44 EDT

*** This bug has been marked as a duplicate of bug 214092 ***