Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340402

Summary: Eclipse running with xulrunner 2.0 crashed on press Ctrl+Space
Product: [Eclipse Project] Platform Reporter: Michal Vyskocil <mvyskocil>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: prakash
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
The crash report from eclipse none

Description Michal Vyskocil CLA 2011-03-18 04:32:15 EDT 
Build Identifier: Eclipse Helios SR1

Moved from https://bugzilla.novell.com/show_bug.cgi?id=679107

I just installed Opensuse 11.4 from the live KDE cd
I run an eclipse Helios build from end 2009, 20091202-2000, downloaded when I
had problems with a previous version of OpenSuse; this was solved via a bug-fix
The first updates installs a Oracle Java 1.6 jre that allows eclipse to run (not
available before first update)
Eclipse starts without errors
Eclipse exits suddenly; it appears to me that eclipse exits when a frame is
opened (for instance, pressing CTRL-spacebar to have completion assistance
always exist eclipse - other actions do, not sure if they would open a frame
within eclipse)
When eclipse exits this way, it just disappears from the screen. When I
re-start eclipse, it does not tell me that a session is already open, a sign
that eclipse exited completely


Reproducible: Always

Steps to Reproduce:
1. Run eclipse Helios with xulrunner 2.0
2. Press Ctrl+Space
3. eclipse crashes
Comment 1 Michal Vyskocil CLA 2011-03-18 04:35:32 EDT 
Created attachment 191486 [details]
The crash report from eclipse

The crash log is moved from http://pastebin.com/y4gVw7v8

Note the reporter confirm the crash disappears when the xulrunner < 2.0 is used
https://bugzilla.novell.com/show_bug.cgi?id=679107#c4
Comment 2 Prakash Rangaraj CLA 2011-03-18 04:57:58 EDT 
This has been fixed in SR2.

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