Bug 1045767 - eclipse frequently segfaults in libjavascriptcoregtk
Summary: eclipse frequently segfaults in libjavascriptcoregtk
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: webkitgtk
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-21 21:11 UTC by Andy Lutomirski
Modified: 2015-05-05 14:32 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-05 14:32:31 UTC
Type: Bug


Attachments (Terms of Use)
Eclipse errror log (155.05 KB, text/x-log)
2013-12-21 21:11 UTC, Andy Lutomirski
no flags Details

Description Andy Lutomirski 2013-12-21 21:11:09 UTC
Created attachment 840154 [details]
Eclipse errror log

I can trigger this bug by deleting ~/.eclipse and the entire contents of ~/workspace and trying to start eclipse pointed at ~/workspace.

If I fiddle with Eclipse and get it to start, causing a suggestion box to pop up by pressing Ctrl-Space on any Java symbol will trigger a crash within two seconds, with the same stack trace.

Comment 1 Andy Lutomirski 2013-12-22 03:49:53 UTC
FWIW, I can trigger the exact same bug in eclipse-standard-kepler-SR1-linux-gtk-x86_64.tar.gz.  Since I doubt that the standard Eclipse distribution is unusable, I'm reassigning this to webkitgtk.

To reproduce: open any Java file in Eclipse and press Ctrl-Enter.  Eclipse will crash after 1-2 seconds.

Comment 2 Roland Grunberg 2014-01-02 18:11:33 UTC
I was able to find Bug 990091 which seems similar to this. The problem would seem to be limited resources or maybe some kind of memory corruption.

As a workaround for now, could you try adding '-Dorg.eclipse.swt.browser.DefaultType=mozilla' to the bottom of /etc/eclipse.ini and see if that eliminates the issue.

Comment 3 Andy Lutomirski 2014-01-02 23:16:40 UTC
Oddly, I can't reproduce this today.  It was 100% reproducible when I filed the bug.

I'll try that as a workaround if I can trigger it again.

Comment 4 Alexander Kurtakov 2015-05-05 06:00:19 UTC
What is the status of this bug? I assume close as there was no action for more than a year?

Comment 5 Kevin Fenzi 2015-05-05 14:32:31 UTC
Sure, lets close for now, and if anyone can reproduce, please file a new bug or reopen with more details.


Note You need to log in before you can comment on or make changes to this bug.