← Back to team overview

openjdk team mailing list archive

[Bug 968308]

 

It does not abort that often on 3.8.2. But 4.3, currently m7, does it an awful lot. The problem remains that there is no certain way to reproduce: sometimes I need to start 4.3m7 several times quickly in succession because as soon as the main window appears and I move the mouse over source code (which would probably show the hover containing source information) Eclipse aborts.
But there are also times that I can work for 3 hours without any problem.

I don't know if it's possible, but the huge problem now is that I can
hardly use 4.3m7 at all. Would it be possible to somehow "guard" against
this exception somewhere in the source code, so that instead of
completely dying the process continues?

In the meantime, if there is anything I can help with to get more
details on this let me know...

-- 
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


References