openjdk team mailing list archive

[Marc-andre-laperle <968308@xxxxxxxxxxxxxxxxxx>]

(In reply to comment #49)
> I've traced through the WebKitGTK source and identified all paths that lead
> to webkitWebViewRegisterForIconNotification().  Once the icons database has
> been disabled these paths all detect this and run away before making this
> call.  By running a WebKitGTK instrumented with fprintf's the only way I can
> see this function possibly being encountered is if one of these paths
> happens before the database has been disabled.
> 
> The Browser's first invocation of webkit_get_favicon_database(), which is
> needed in order to disable it, seems like the only place where this could
> happen in theory, because it creates a background thread that can ultimately
> invoke webkitWebViewRegisterForIconNotification() after re-joining the main
> thread.  The timing of this re-join is of course variable.  In testing I was
> never able to get this case to actually happen, but I did see some variance
> in ordering that occurred as a result of the thread join happening at
> different times.

Are you sure it has something to do with
webkitWebViewRegisterForIconNotification? I'm thinking what's being
reported in hs_err is wrong because my core dumps show a different call
stack (see previous comment).

> I've changed the fix in the 4.4 stream to only run for the first
> WebKitGTK-based Browser since the icons database is shared amongst all
> instances.  I'd like to put the change in 4.3.1, and am reasonably sure that
> it's not dangerous, but the fact that the crash has been seen in the 4.4
> stream is a bit discouraging.  Does the frequency of this crash seem at
> least diminished in 4.4 from what it was in 4.3?

It greatly varies. It didn't crash for a few days but I crashed 3 times
the same day, I'm at 6 this week.

-- 
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in Ubuntu.
https://bugs.launchpad.net/bugs/968308

Title:
  Opening Eclipse workbench causes SIGSEGV

Status in Eclipse:
  Confirmed
Status in “openjdk-6” package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 12.04 updated kernel 3.3.0-030300-generic x86_64.
  To reproduce:
   - Do fresh install of eclipse
   - open eclipse
   - click on Workbench icon

  The following error occurs:

  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x00007f611eb2f5e0, pid=11709, tid=140057214498560
  #
  # JRE version: 6.0_24-b24
  # Java VM: OpenJDK 64-Bit Server VM (20.0-b12 mixed mode linux-amd64 compressed oops)
  # Derivative: IcedTea6 1.11.1
  # Distribution: Ubuntu precise (development branch), package 6b24-1.11.1-3ubuntu3
  # Problematic frame:
  # C  [libwebkitgtk-1.0.so.0+0x3da5e0]  webkitWebViewRegisterForIconNotification+0xc0

  See attached error log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/968308/+subscriptions