Eclipse crash

Created attachment 226958
JVM dump

At random, mostly very inopportune times Eclipse 4.3m5 crashes (creating a JVM dump). The dump will be attached after this. I have no reproduction scenario.

Which Linux distro are you using?

I'm using Ubuntu 12.12 64-bit. I also posted a hang that might be related (bug 400723)- I get the feeling it might be related to the browser integration which if I remember correctly is used inside hover popups.

This bug has made it impossible to use this milestone, sadly enough- it crashes tens of times a day. Is there a way to disable webkit? Or to replace it with the old xulrunner?

You can change the Browser's default renderer type by adding the following vm arg to the end of your eclipse.ini:

-Dorg.eclipse.swt.browser.DefaultType=mozilla

You can then point at a XULRunner to use by adding vm arg:

-Dorg.eclipse.swt.browser.XULRunnerPath=<fullPath>

(note the list of supported XULRunner versions: http://www.eclipse.org/swt/faq.php#browserlinux )

FYI: this same bug now also occurs several times per hour on Eclipse 3.8.2, when it runs on Ubuntu 13.04. Yes, I know it is not yet released, just adding info.

*** Bug 401603 has been marked as a duplicate of this bug. ***

*** Bug 396577 has been marked as a duplicate of this bug. ***

To update, I haven't been able to reproduce this yet (using 3.8.2 on several different Ubuntu versions, closing the initial Welcome screen by clicking its 'X'). Am continuing to look into this, but will be difficult to track down if it's not reproducible.

(In reply to comment #8)
> To update, I haven't been able to reproduce this yet (using 3.8.2 on several
> different Ubuntu versions, closing the initial Welcome screen by clicking
> its 'X'). Am continuing to look into this, but will be difficult to track
> down if it's not reproducible.

I've seen it on 3.x only with Ubuntu 12.04, but that was via VNC.

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

(In reply to comment #10)

You should be able to avoid this as described in comment 4 (eg.- point -Dorg.eclipse.swt.browser.XULRunnerPath at a downloaded XULRunner 10). If you're fine with running with no browser support at all (Eclipse works generally fine without it by providing content in alternate ways if Browser creation fails), you can set this property to /dev/null .

This bug just appeared for me on ArchLinux. The changes I made before it appeared was installing FreeNX (and xfce but I don't think that's as important).

FreeNx has a dependency on nx-common wich installs libjpeg8.0.2 libpng16.2.0

If I'm not mistaken these have been involved in previous crashes revolving around 'notifications when hovering a variable/type/etc'.

Posting my hs_err dump aswell

Created attachment 231232
hs_err dump from archlinux with freenx installed (lipng16.2.0 libjpeg8.0.2)

Here's another possible solution: http://aleksz-programming.blogspot.de/2013/03/eclipse-and-webkit-on-ubuntu-64.html

Replace libwebkitgtk-1 with libwebkitgtk-3

(In reply to comment #14)
> Replace libwebkitgtk-1 with libwebkitgtk-3
Thanks a million for posting this!
I removed the libwebkitgtk-1.0* files to test. Eclipse starts normally and hovers work, but they do not seem to use a browser window anymore: they look like text input boxes with only rudimentary formatting of the html javadoc.

Looking at what libraries are open (lsof -p) I see that webkitgtk-3* is not used at all - so clearly eclipse is not automatically picking up libwebkitgtk-3 but just not using libwebkitgtk at all. Which is so far fine by me - not dying has priority ;-)

(In reply to comment #14)

Deleting this library just disables the browser altogether. A better way of doing the same thing is described in comment 4 (-Dorg.eclipse.swt.browser.XULRunnerPath can be set to a value like "/dev/null" if you don't have a supported XULRunner release to point at).

Regarding GTK3, you can run your Eclipse download (as of Eclipse 4.3) with GTK3 libraries instead of GTK2, which may or may not help with this case. To try this, set Linux environment variable SWT_GTK3=1 before launching eclipse. Note that the GTK3 port of SWT is currently considered to be early access.

(In reply to comment #16)
> (In reply to comment #14)
> Regarding GTK3, you can run your Eclipse download (as of Eclipse 4.3) with
> GTK3 libraries instead of GTK2
Heh, that dies immediately with:

# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff2be8a8d98, pid=32672, tid=140683416110848
#
# JRE version: 7.0_21-b02
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-3.0.so.0+0x3fcd98] DumpRenderTreeSupportGtk::setComposition(_WebKitWebView*, char const*, int, int)+0x8d28

I am surprised I seem to be one of the few people having this.. Since it's close to 4.3 release I sure hope I'm the exception..

*** Bug 408843 has been marked as a duplicate of this bug. ***

Hi Grant. We've been getting this crash here (3 of us on Ubuntu 13.04). We all enabled core dumps and installed libwebkitgtk-1.0-0-dbg so hopefully we can help provide more information.

The first core dump we got doesn't contain webkitWebViewRegisterForIconNotification so it might be a different bug, I'm not sure.

<signal handler called>() at 0x7fb7c2ba60b0
WebKit::core() at /build/buildd/webkit-1.10.2/build-2.0/../Source/WebKit/gtk/webkit/webkitwebview.cpp:5,368 0x7fb7268cf6d5
WebKit::GtkAdjustmentWatcher::updateAdjustmentsFromScrollbars() at /build/buildd/webkit-1.10.2/build-2.0/../Source/WebKit/gtk/WebCoreSupport/GtkAdjustmentWatcher.cpp:65 0x7fb7268a8108
WebKit::updateAdjustmentCallback() at /build/buildd/webkit-1.10.2/build-2.0/../Source/WebKit/gtk/WebCoreSupport/GtkAdjustmentWatcher.cpp:76 0x7fb7268a8189

the line is
WebKitWebViewPrivate* priv = webView->priv;

so I guess webView is wrong. Let me know if you want the core file (1.9 GB!!).

*** Bug 400723 has been marked as a duplicate of this bug. ***

Looking at webkitWebViewRegisterForIconNotification(), either webview is invalid (retrieved from a WebKitWebFramePrivate) or webview->priv is invalid. I've tried various things with the content assist and hover help browsers to try to make this happen but still haven't seen this crash (Ubuntu 12.10 with webkitgtk 1.10.0). I'll try with Ubuntu 13 next week, but I don't anticipate this making a difference since its webkitgtk libraries are approximately the same.

Hi,

I began with this type of problems when I upgraded to Ubuntu 13.04.

A trick is to reset the view when the problem arise.

Thank you for your work.

Created attachment 232182
Another crask log

Ubuntu 13.04 (kernel 3.9.4). Juno 4.2.2, JDT, Egit (from Juno repo)

Hi,
I experience a crash at least 5 times per days. I have to restrat my computer because on next strat eclispe pop up error about PHP debug view and it is not usable.
I've attach on of the a pid log file

With Ubuntu 13.04 I had a case crashing almost consistently earlier, at either webkitWebViewRegisterForIconNotification() or DumpRenderTreeSupportGtk::setComposition() (like comment 23). It only happened with openjdk7, never with an IBM JRE. However this case no longer crashes for me with any JRE.

Regardless, it's obviously very timing-dependent, which makes me suspicious of BrowserInformationControl.setVisible()'s invocation of readAndDispatch(), which appears in the attached dumps right before the crash. This can make an event run before it should, which frequently causes problems like native null ptr's. I'm going to see if changing this class' implementation to no longer spin the event loop seems helpful.

Ok, I will try with the standard JRE, but I've already try and I experience other crash. I'll do that and give you more information.

I've got a crash with standard JRE but not pid file just the /var/crash report (310Mo) impossible to upload on this site. I'll try to cut the dump and just past the header part.

Created attachment 232214
At least the .log file of .metadata

Created attachment 232216
The apport crash report without core Dump

Another crash. I go back with openJDK at least crash appens but not all 5 minutes

Using Eclipse Juno 4.2 and Ubuntu 13.04 there are some problems with libwebkitgtk, as reported in this bug and as I reporter with error and log files.

Using Eclipse Juno 4.2 and Ubuntru 13.04 on amd64 architecture, the system crash without any information. No Java stack and no information saved in log file.

Eclipse on Ubuntu seemes to work no so well as in past did.

Created attachment 232362
patch to disable icons database (apply post-4.3)

Determining the root cause of this has proven to be quite difficult. Even compiling WebKitGTK from source with instrumentation did not help because its characteristics did not match the WebKitGTK that's shipped with Ubuntu.

Anyways, one thing I was able to determine from the instrumented WebKitGTK is that the path that crashes is never run if WebKit's icons database is disabled (disabling this is not uncommon). So the current proposed fix is to disable the icons database since the Browser does not use it in any way. Hopefully this will prove to be adequate.

The patch for this is attached. It will be put into the 4.4 stream as soon as it is open, and if it proves to work well over the summer then it will be back-ported to the 4.3.1 stream as well.

(In reply to comment #32)
> Created attachment 232362 [details]
> patch to disable icons database (apply post-4.3)
>
> Determining the root cause of this has proven to be quite difficult. Even
> compiling WebKitGTK from source with instrumentation did not help because
> its characteristics did not match the WebKitGTK that's shipped with Ubuntu.

I think you should be able to get the matching source with:
apt-get source libwebkitgtk-1.0-0

> Anyways, one thing I was able to determine from the instrumented WebKitGTK
> is that the path that crashes is never run if WebKit's icons database is
> disabled (disabling this is not uncommon). So the current proposed fix is
> to disable the icons database since the Browser does not use it in any way.
> Hopefully this will prove to be adequate.
>
> The patch for this is attached. It will be put into the 4.4 stream as soon
> as it is open, and if it proves to work well over the summer then it will be
> back-ported to the 4.3.1 stream as well.

It's open now, I believe.

Fixed > 20130625 in the 4.4 stream, commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=76d7d429442fe73692a90b1854cf0455cb3d83fa .

If crashes are seen in WebKitGTK-based Browsers in native frames other than webkitWebViewRegisterForIconNotification() then please log separate reports. This report deals specifically with this case.

Leaving report open and settings its Target Milestone to 4.3.1 as a reminder to include this fix in 4.3.1 if it proves to work well in the 4.4 stream in the interim.

Created attachment 233150
Crash after fix

Unfortunately, I got this crash again using 4.4.0-I20130702-1230.

(In reply to comment #35)
> Unfortunately, I got this crash again using 4.4.0-I20130702-1230.

I've taken a look and see that the fix is not in there. It's in the latest nightly builds, but I-builds require an explicit submit from the component, and it looks like SWT did not do this for 4.4.0-I20130702-1230. I'll ensure that we submit for the next I-build.

*** Bug 412235 has been marked as a duplicate of this bug. ***

Hi all, I repoduce this bug on 4.3 with SWT_GTK3=1. I'll attacht the pid error file

In ubuntu 13.10, if a set SWT_GTK3=1 as global variable, the menus of Eclipse disappear.

(In reply to Francesco D\'Amore from comment #64)
> In ubuntu 13.10, if a set SWT_GTK3=1 as global variable, the menus of
> Eclipse disappear.

Have you tried undefining UBUNTU_MENUPROXY? like UBUNTU_MENUPROXY=

No.
In order to make manu working in Eclipse Kepler and Ubuntu 13.10, a just changed some things in the launcher.

But this work around seems don't work if a set SWT_GT3=1.

All these errors are very annoying for Ubuntu users... Eclipse appear very unusable. Today it crashed five times in three hours!

In order to (In reply to Marc-Andre Laperle from comment #65)
> (In reply to Francesco D\'Amore from comment #64)
> > In ubuntu 13.10, if a set SWT_GTK3=1 as global variable, the menus of
> > Eclipse disappear.
>
> Have you tried undefining UBUNTU_MENUPROXY? like UBUNTU_MENUPROXY=

Created attachment 237557
JAVA crash

java crash

(In reply to Francesco D\'Amore from comment #66)
> No.
> In order to make manu working in Eclipse Kepler and Ubuntu 13.10, a just
> changed some things in the launcher.
>
> But this work around seems don't work if a set SWT_GT3=1.

Can you describe your workaround? Or perhaps a link to it? I might look into fixing this menu issue soon and any information is useful.

> All these errors are very annoying for Ubuntu users... Eclipse appear very
> unusable. Today it crashed five times in three hours!

So far, everything as led me to believe that this particular crash has been fixed in webkit and Ubuntu will get an updated version in Ubuntu 14.04. I have applied the fix locally on my 13.10 and haven't seen the crash since. I would attach the .deb files here but I don't think this would sit well with Eclipse policy since they are not EPL (?).

(In reply to Marc-Andre Laperle from comment #68)
> I would attach the .deb files here but I don't think this would sit well with

Probably not. Unfortunately the release date for Ubuntu 14.04 is still far out. Perhaps the Fedora 20 release will ship with it.

Are you running with 4.3.1 or a 4.4-stream build? I'm wondering if the comment 34 change could be relevant, which is only in the 4.4 stream.

(In reply to Grant Gayed from comment #69)
> (In reply to Marc-Andre Laperle from comment #68)
> Are you running with 4.3.1 or a 4.4-stream build? I'm wondering if the
> comment 34 change could be relevant, which is only in the 4.4 stream.

Unfortunately, I'm running the 4.4 stream and got the crash multiple times after the SWT fix, although it didn't manifest itself for a few days. Then I applied the webkit fix and everything was fine.

I also tested without the webkit fix when I upgraded to Ubuntu 13.10 and at that time SWT was switched to use GTK3 by default and I got the crash again. I have patched my webkit again and so far so good.

> > I would attach the .deb files here but I don't think this would sit well with
>
> Probably not. Unfortunately the release date for Ubuntu 14.04 is still far
> out. Perhaps the Fedora 20 release will ship with it.

If only this bug was easier to reproduce, the webkit patch could be verified and it would make a better case for applying the patch to 13.10.

Created attachment 237569
Test project

Grant, could you try this test project and see if you are seeing the crash? I can get it in a couple of seconds. Steps to reproduce:

Using 4.4 I20131119-0800, Ubuntu 13.10 64 bit

1. Open "Test Browser" view
2. Maximize the view (Double-click on the tab)
3. Move around the mouse a bit inside the view (optional?)

Sometimes I get the DumpRenderTreeSupportGtk crash, sometimes the webkitWebViewRegisterForIconNotification but when I open the core file with gdb they both show the back trace with the updateAdjustmentsFromScrollbars call.

This is exactly the two bug notification i've got before. Like I said, with 13.04 and 20130919-0819 I don't get it anymore. It's strange because I don't think the patch on webKit was apply into ubuntu, but it seems to be the cause of these crash.

(In reply to Florian HENRY from comment #72)
> This is exactly the two bug notification i've got before. Like I said, with
> 13.04 and 20130919-0819 I don't get it anymore. It's strange because I don't
> think the patch on webKit was apply into ubuntu, but it seems to be the
> cause of these crash.

Do you still have the packages libwebkitgtk-1.0-0 and libwebkitgtk-1.0-common installed? I still get the crash on 13.04, 20130919-0819 when I test with the attached project.

I don't understand
1-Open "Test Browser" view

I import the projet into eclipse, I can see it, it didn't crash. Do you mean run it as Java application, or Applet ? I try without succes.

I'm sorry, I use Eclipse for PHP, I never develop java application with it so i don't know exactly what to do.
I have SWT_GTK3=1 in my launch script
and
libwebkitgtk-1.0-0 install
libwebkitgtk-1.0-common install
libwebkitgtk-3.0-0 install
libwebkitgtk-3.0-common install

(In reply to Marc-Andre Laperle from comment #68)
> So far, everything as led me to believe that this particular crash has been
> fixed in webkit and Ubuntu will get an updated version in Ubuntu 14.04. I
> have applied the fix locally on my 13.10 and haven't seen the crash since. I
> would attach the .deb files here but I don't think this would sit well with
> Eclipse policy since they are not EPL (?).

I believe you can just share the .deb files via dropbox or similar service. In the end, WebKitGTK is an open source project and redistribution is allowed.

Could you explain in more details about the fix you applied? Is this an official newer version of WebKitGTK? Or you patched the one in Ubuntu 13.04 and rebuilt it?

(In reply to Marc-Andre Laperle from comment #68)
> Can you describe your workaround? Or perhaps a link to it? I might look into
> fixing this menu issue soon and any information is useful.

My eclipse launcher, showd in Unity toolbar, is a file stored in:
/home/<myhome>/.local/share/applications/eclipse.desktop

This is my launcher:
[Desktop Entry]
Encoding=UTF-8
Version=1.0
Type=Application
Name=Java - Eclipse
Icon=eclipse.png
Path=/home/<myhome>/eclipse
Exec=env UBUNTU_MENUPROXY= /home/<myhome>/eclipse/eclipse
StartupNotify=false
StartupWMClass=Eclipse
OnlyShowIn=Unity;
X-UnityGenerated=true

In order to make menus working, you should add this line:
Exec=env UBUNTU_MENUPROXY= /home/<myhome>/eclipse/eclipse

My Eclipse is installed in /home/<myhome>/eclipse

> So far, everything as led me to believe that this particular crash has been
> fixed in webkit and Ubuntu will get an updated version in Ubuntu 14.04. I
> have applied the fix locally on my 13.10 and haven't seen the crash since. I
> would attach the .deb files here but I don't think this would sit well with
> Eclipse policy since they are not EPL (?).

Can you describe this webkit fix in more details??? Can you provide us with a link? Is very important to overcame this issue.... Eclipse in ubuntu 13.10 is unstable....

(In reply to Florian HENRY from comment #74)
> I don't understand
> 1-Open "Test Browser" view
>
> I import the projet into eclipse, I can see it, it didn't crash. Do you mean
> run it as Java application, or Applet ? I try without succes.

Sorry this message was directed to Grant so I didn't add as much detail. More steps:
0. Import the project in Eclipse. It's a plug-in project so you'll need PDE installed (Eclipse SDK, Classic, etc have it).
0.1 Run as Eclipse Application so that you get the view inside the launched Eclipse.

(In reply to Kaloyan Raev from comment #75)
> (In reply to Marc-Andre Laperle from comment #68)
> I believe you can just share the .deb files via dropbox or similar service.
> In the end, WebKitGTK is an open source project and redistribution is
> allowed.

Thanks for the suggestion, I was looking for something like that.

> Could you explain in more details about the fix you applied? Is this an
> official newer version of WebKitGTK? Or you patched the one in Ubuntu 13.04
> and rebuilt it?

I applied the fix locally on top of the Ubuntu 13.04 package then I patched it again when I upgraded to Ubuntu 13.10. The fix is included in later official versions of Webkit. I'm not sure exactly which version will get into 14.04 but it looks like it will be 2.3.1 (proposed) which includes the fix. The webkit bugzilla link has been posted before but I'll give you the direct link to the patch:
https://bug-119003-attachments.webkit.org/attachment.cgi?id=207317

(In reply to Francesco D\'Amore from comment #76)
> In order to make menus working, you should add this line:
> Exec=env UBUNTU_MENUPROXY= /home/<myhome>/eclipse/eclipse

Ah OK, I was referring to the same thing, we just misunderstood each other a little bit.

(In reply to Kaloyan Raev from comment #75)
> I believe you can just share the .deb files via dropbox or similar service.
> In the end, WebKitGTK is an open source project and redistribution is
> allowed.

Here are the patched .deb files for 13.10 64 bit:
https://www.dropbox.com/l/3fsKx3y53bmVoe80asoVKb

It doesn't include the optional debugging symbols (-dbg packages) because they are quite big (> 1GB!).

(In reply to Marc-Andre Laperle from comment #71)
> Grant, could you try this test project and see if you are seeing the crash?
>
> 1. Open "Test Browser" view
> 2. Maximize the view (Double-click on the tab)
> 3. Move around the mouse a bit inside the view (optional?)

Your view crashes reliably for me if step 3 is replaced by "close the view (crash!)". My Ubuntu is 13.04 and my VM is from IBM, which could account for the difference in the timing of the crashes (eg.- memory getting corrupted once the view is maximized but the IBM VM gets lucky and tolerates it longer than the Oracle VM).

*** Bug 421891 has been marked as a duplicate of this bug. ***

(In reply to Grant Gayed from comment #79)
> Your view crashes reliably for me if step 3 is replaced by "close the view
> (crash!)".

Thanks for reproducing it!

Here are the patched .deb files for 13.04 64 bit:
https://www.dropbox.com/l/fdlcEeDRbVoHuivn6RNLyd

Sorry for trivial question...

I would like to apply the patch for ubuntu 13.10. In the tar file included in dropbox there are 15 .deb files.

Do I install each files in order to apply the patch?

Thank you...

(In reply to Francesco D\'Amore from comment #82)
> Do I install each files in order to apply the patch?

You need to at least install (i.e. upgrade) all the ones you have currently installed otherwise you will most likely have broken dependencies. All the packages included in the tar are built from the same webkit source tree so they all have the same Ubuntu version. If an update comes from Ubuntu they will all get replaced. You can install/upgrade only the ones you have currently installed but I think it's easier to just install all of them:

sudo dpkg -i *.deb

If you want to revert to the original packages from Ubuntu servers, you can specify /saucy when re-installing the packages with apt-get, for example:

sudo apt-get install gir1.2-javascriptcoregtk-*/saucy gir1.2-webkit-*/saucy libjavascriptcoregtk-*/saucy libwebkit-dev/saucy libwebkitgtk*/saucy

For 13.04 it would be /raring.

Let me know if you see an improvement. On our end, we tested the fix on 5 different PCs and VMs using the test plug-in I attached and it seemed to resolved the issue. Keep in mind that there are other possible crashes so check your crash log.

Even after the patch the problem arise more and mor, working with Eclipse.

Unfortunatly there aren't JVM crash files available for logging.

Are you experienced the same issue?

Thank you.

(In reply to Francesco D\'Amore from comment #84)
> Unfortunatly there aren't JVM crash files available for logging.
Well, I had that too; I managed to get proper jvm logfiles by using a start script instead of Eclipse's launcher. Create a file "start.sh" in your eclipse home with:

#!/bin/bash
ulimit -c unlimited
/opt/java/jdk1.7.0_25/bin/java -XX:MaxPermSize=512m -Xmx2048m -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null -Dorg.eclipse.swt.browser.DefaultType=mozilla -jar plugins/org.eclipse.equinox.launcher_*.jar -console

Mark it executable (chmod a+x start.sh) and use it to start Eclipse. This at least produces the jvm logs again.

In addition, for me Eclipse on Ubuntu 13.04 has been *rock solid*, both 4.2 and 4.3, no crashes *at all* with daily use for many hours a day (yes, lack of real life ;-) by doing the following:

* Disable browser support by adding the
-Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null
-Dorg.eclipse.swt.browser.DefaultType=mozilla
parameters to eclipse.ini

* Apply the workaround for bug# 416869:
sudo apt-get remove overlay-scrollbar

With those things no crashes.

Thank you Frits... I will try it.

I hope that in the next releases, of both Eclipse and Ubuntu, these problems will be fixed.

(In reply to Frits Jalvingh from comment #85)
> (In reply to Francesco D\'Amore from comment #84)
> > Unfortunatly there aren't JVM crash files available for logging.
> Well, I had that too; I managed to get proper jvm logfiles by using a start
> script instead of Eclipse's launcher. Create a file "start.sh" in your
> eclipse home with:
>
> #!/bin/bash
> ulimit -c unlimited
> /opt/java/jdk1.7.0_25/bin/java -XX:MaxPermSize=512m -Xmx2048m
> -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null
> -Dorg.eclipse.swt.browser.DefaultType=mozilla -jar
> plugins/org.eclipse.equinox.launcher_*.jar -console
>
> Mark it executable (chmod a+x start.sh) and use it to start Eclipse. This at
> least produces the jvm logs again.
>
> In addition, for me Eclipse on Ubuntu 13.04 has been *rock solid*, both 4.2
> and 4.3, no crashes *at all* with daily use for many hours a day (yes, lack
> of real life ;-) by doing the following:
>
> * Disable browser support by adding the
> -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null
> -Dorg.eclipse.swt.browser.DefaultType=mozilla
> parameters to eclipse.ini
>
> * Apply the workaround for bug# 416869:
> sudo apt-get remove overlay-scrollbar
>
> With those things no crashes.

(In reply to Francesco D\'Amore from comment #84)
> Even after the patch the problem arise more and mor, working with Eclipse.
>
> Unfortunatly there aren't JVM crash files available for logging.
>
> Are you experienced the same issue?
>
> Thank you.

Hi Francesco. There are a few other bugs that could be still affecting you. The other crash that I got really often is the one related to overlay-scrollbar triggering a stack overflow. I also saw this on a colleague's 13.04. Could you try still using webkit but disabling overlay-scrollbar?

sudo apt-get remove overlay-scrollbar
or start Eclipse with LIBOVERLAY_SCROLLBAR=0 environment variable.

I'm trying to get webkit fixed in Ubuntu by backporting the fix so any help in testing is appreciated.

One other crash is Bug 420550, but it should be unrelated to webkit or overlay-scrollbar.

Ok...

I will apply the fix next week.

Thank you for your help.

(In reply to Marc-Andre Laperle from comment #87)
> (In reply to Francesco D\'Amore from comment #84)
> > Even after the patch the problem arise more and mor, working with Eclipse.
> >
> > Unfortunatly there aren't JVM crash files available for logging.
> >
> > Are you experienced the same issue?
> >
> > Thank you.
>
> Hi Francesco. There are a few other bugs that could be still affecting you.
> The other crash that I got really often is the one related to
> overlay-scrollbar triggering a stack overflow. I also saw this on a
> colleague's 13.04. Could you try still using webkit but disabling
> overlay-scrollbar?
>
> sudo apt-get remove overlay-scrollbar
> or start Eclipse with LIBOVERLAY_SCROLLBAR=0 environment variable.
>
> I'm trying to get webkit fixed in Ubuntu by backporting the fix so any help
> in testing is appreciated.
>
> One other crash is Bug 420550, but it should be unrelated to webkit or
> overlay-scrollbar.

(In reply to Marc-Andre Laperle from comment #87)

I can confirm that the test case stopped crashing for me after applying the comment 81 packages.

I don't use Eclipse on Ubuntu on a frequent enough basis to confirm/refute a change in its regular day-to-day use.

Thank you Frits.

After applying the patch related to webkit and scrollbar, as you suggested, eclipse seems to be very robust and stable.

Take in consideration that I installed also the .deb files about webwkit, suggested in #comment 83

After two days coding, eclipse not crash yet.

(In reply to Frits Jalvingh from comment #85)
> (In reply to Francesco D\'Amore from comment #84)
> > Unfortunatly there aren't JVM crash files available for logging.
> Well, I had that too; I managed to get proper jvm logfiles by using a start
> script instead of Eclipse's launcher. Create a file "start.sh" in your
> eclipse home with:
>
> #!/bin/bash
> ulimit -c unlimited
> /opt/java/jdk1.7.0_25/bin/java -XX:MaxPermSize=512m -Xmx2048m
> -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null
> -Dorg.eclipse.swt.browser.DefaultType=mozilla -jar
> plugins/org.eclipse.equinox.launcher_*.jar -console
>
> Mark it executable (chmod a+x start.sh) and use it to start Eclipse. This at
> least produces the jvm logs again.
>
> In addition, for me Eclipse on Ubuntu 13.04 has been *rock solid*, both 4.2
> and 4.3, no crashes *at all* with daily use for many hours a day (yes, lack
> of real life ;-) by doing the following:
>
> * Disable browser support by adding the
> -Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null
> -Dorg.eclipse.swt.browser.DefaultType=mozilla
> parameters to eclipse.ini
>
> * Apply the workaround for bug# 416869:
> sudo apt-get remove overlay-scrollbar
>
> With those things no crashes.

Just FYI: the problem is still present in Eclipse Luna 4.4m6, but now in webkit 3.0. The problem I got after 15 seconds of use was:

# SIGSEGV (0xb) at pc=0x00007ff32d652345, pid=17155, tid=140685029988096
#
# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-3.0.so.0+0x407345] webkitWebViewRegisterForIconNotification+0x95

Java 8, 64-bit up-to-date Ubuntu 13.10, and Luna I from 2014-03-18, crashed 3 times within an hour when doing "quick fixes" in JDT, at webkitWebViewRegisterForIconNotification - though I lost the traceback while hunting for my eclipse.org account.

Can you try latest I-build with export SWT_WEBKIT2=true ? There is experimental webkit2 support which runs certain things out of process thus improves stability greatly.

(In reply to Alexander Kurtakov from comment #93)
> Can you try latest I-build with export SWT_WEBKIT2=true ? There is
> experimental webkit2 support which runs certain things out of process thus
> improves stability greatly.

I'm testing the latest I-build as you suggested. seems to be ok since hours, but I needed to include SWT_GTK3=0 in order to edit VM properties in the laucher configurations dialog or select items in an import from existent installation dialog.

*** Bug 432395 has been marked as a duplicate of this bug. ***

I see sometimes this issue when launching an RCP app from Eclipse 3.8.2 on Ubuntu 12.04 32 bits. When starting RCP app with clean workspace it opens the Welcome page with in its turn creates the browser which when crushes with:

# Problematic frame:
# C [libwebkitgtk-1.0.so.0+0x19ed71] webkitWebViewRegisterForIconNotification+0xe1
#

For me, now on Ubuntu 14.04 and Eclipse Version: Kepler Service Release 2, the tips give on comment 85 solve this bug.
Eclipse do not crash anymore (full day uses). Sometime it still crash on syncronize view but it's another problem

*** Bug 434571 has been marked as a duplicate of this bug. ***

This seems similar to Bug 409300. Should that be marked as a duplicate of this?

I am closing this as NOT_ECLIPSE because a fix is provided in recent versions of Webkit and with the updated version in Ubuntu 14.04, the crash doesn't happen. Also, I patched the package in 13.10 in a way to backport the fix which was believed to address the issue and I could not reproduce the crash in months of use. The patch is available on launchpad if the Ubuntu team wants to fix it in previous Ubuntu releases (or if a user wants to patch it locally), see https://bugs.launchpad.net/ubuntu/+source/webkit/+bug/1160411

Created attachment 244626
crash dump file

(In reply to ayush agarwal from comment #101)
> Created attachment 244626 [details]
> crash dump file

See bug 404776.