SIGSEGV in runtime environment when starting Eclipse runtime workbench

[Bruno Girin]

When starting a Runtime Workbench to debug a plugin, I get the following error when trying to dismiss the welcome screen:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f87966c26de, pid=15716, tid=140222551627520
#
# JRE version: 7.0_15-b20
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-1.0.so.0+0x4246de] webkitWebViewRegisterForIconNotification+0xbe
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/bruno/hs_err_pid15716.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

This is probably related to defects #1055159 and #1086831. However, it seems to happen in a different frame than the other two and under different conditions.

I am using Eclipse 3.8 on Raring.

[Timo Witte (spacefish)]

I have the same problem, i attached a more detailed hs_err with coredump info included...
For me it happens as soon as a Code autocomplete is shown on screen!

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marc-Andre Laperle (malaperle)]

This appears to be fixed upstream, see https://bugs.webkit.org/show_bug.cgi?id=119003. Also, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=400626 for some more investigation.

Is it possible to update the package from upstream for Raring? This crash is affecting a lot of Eclipse users. Let me know how I can help.

[Grant Gayed (grant-gayed)]

Note https://bugs.eclipse.org/bugs/show_bug.cgi?id=400626#c48 in particular, which explains why the stack in https://bugs.webkit.org/show_bug.cgi?id=118396 (marked as a duplicate of the WebKit bug with the fix) is not the same as the stack in this report. I don't think that we know for sure that the upstream change will fix this issue, but the theory is that it's the underlying problem that leads to this report's crash since it was in the dump from gdb.

[razor7 (ghiamar)]

Hi, It is possible to update that particular package in Ubuntu 13.04? thanks

[Torsten Krah (tkrah)]

Some chance to get this fix into raring soon?

[Marc-Andre Laperle (malaperle)]

I'm trying to backport the fix and push the branch to launchpad so that it can be proposed but I'm having a lot of trouble. I'm hoping someone can help me.

I did this:

bzr branch lp:ubuntu/saucy/webkit

Then got this error:

bzr: ERROR: Revision {<email address hidden>} not present in "Graph(StackedParentsProvider(bzrlib.repository._LazyListJoin(([CachingParentsProvider(None)], []))))".

I found out I could use -Olaunchpad.packaging_verbosity=off to bypass the error, so I did:

bzr branch lp:ubuntu/saucy/webkit -Olaunchpad.packaging_verbosity=off

But the code seems very out of date:

bzr log -r-1

revno: 46
tags: 1.9.2-1ubuntu4
fixes bug: https://launchpad.net/bugs/1028486
author: Micah Gersten <email address hidden>
committer: Package Import Robot <email address hidden>
branch nick: quantal-proposed
timestamp: Tue 2012-07-24 05:03:22 -0500

But the current version is actually 1.10.2-0ubuntu2. Is there an alternate way to do this? I'll attach the backported patch at least.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "03_adjustmentwatcher_crash.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Marc-Andre Laperle (malaperle)]

Hello,

I have been running Eclipse with webkit patched with the attached patch for months now and it does fix the crash. I also provided a way to reproduce the crash, see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=400626#c71

The attached patch (03_adjustmentwatcher_crash.patch) is a simple backport of the fix available upstream for this bug:
https://bugs.webkit.org/show_bug.cgi?id=119003

Is there any chance this could be accepted in saucy? What can I do to help the process?