Bug 279932 - Eclipse crashes when saving plugin-dependencies
Summary: Eclipse crashes when saving plugin-dependencies
Status: RESOLVED DUPLICATE of bug 214092
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.5   Edit
Hardware: Macintosh Mac OS X
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 08:46 EDT by Robert Gruendler CLA
Modified: 2009-06-11 09:53 EDT (History)
3 users (show)

See Also:

Attachments
osx crash log (75.06 KB, text/plain)
2009-06-11 09:12 EDT, Robert Gruendler 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 Robert Gruendler CLA 2009-06-11 08:46:42 EDT 
Build ID: I20090605-1444

Steps To Reproduce:
1. Create a plugin project
2. Open plugin.xml / Either with graphical editor or text editor
3. Add a plugin dependency
4. Save the plugin.xml

Eclipse crashes at this point with a segmentation fault.


More information:
This is the last info in the terminal:

Invalid memory access of location 00000000 rip=17b25767

Segmentation fault


My System:

OSX 10.5.6
Eclipse Cocoa 64bit version running on java 1.6.0, by adding:

-vm
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Commands/java

to eclipse.ini
Comment 1 Olivier Thomann CLA 2009-06-11 08:51:47 EDT 
Might be a SWT issue.
Moving to SWT.
Could you please provide the crash log.
Comment 2 Robert Gruendler CLA 2009-06-11 09:12:15 EDT 
Created attachment 138925 [details]
osx crash log
Comment 3 Robert Gruendler CLA 2009-06-11 09:13:40 EDT 
I've started eclipse with the java 1.5 32 bit VM, and it does not crash when saving dependencies.
Comment 4 Olivier Thomann CLA 2009-06-11 09:20:01 EDT 
It could also be a JIT bug.
Try to start your 1.6 VM with the option -Djava.compiler=NONE.
Comment 5 Kevin Barnes CLA 2009-06-11 09:53:46 EDT 
There is a new Java 6 VM available from the Apple Developer Connection that will resolve this issue. 

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