Nice idea, David but no luck for me.
I start Eclipse with:
GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
./adt-bundle-linux-x86_64-20131030/eclipse/eclipse -data .
and do Ctrl-F, and click on Find, Find, Close. Eclipse aborts at
g_object_get_qdata+0x18
I restart Eclipse, find the PID, and do:
$ taskset -p 0x00000001 32060
pid 32060's current affinity mask: f
pid 32060's new affinity mask: 1
so, it appears to have worked. I execute the same sequence and Eclipse
aborts at g_object_get_qdata+0x18. Also note:
# An error report file with more information is saved as:
# /home/derek/.../hs_err_pid32060.log
so I had the right PID.
On Thu, Apr 10, 2014 at 10:28 PM, David Matějček <1241...@bugs.launchpad.net
> wrote:
> I use Eclipse Kepler 4.3.2 and this bug occurs more often then ever before!
> Eclipse also is not the only application crashing with this bug - today I
> have seen bugreport also for Gimp.
>
> Workaround:
> 1) Start the Eclipse
> 2) find pid of the process
> 3) taskset -p 0x00000001 <pid>
>
> The problem is something like with volatile and synchronized; with this I
> used two Eclipse instances for 12 hours without a crash!
> After restart I forgot to set it again and Eclipse crashed after 5 minutes
> ...
>
> Now again with taskset after 2 hours no problem.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1241101
>
> Title:
> Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions
>
--
derek
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1241101
Title:
Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Status in Eclipse:
Confirmed
Status in “gtk+2.0” package in Ubuntu:
Triaged
Status in “unity” package in Ubuntu:
Invalid
Status in “gtk+2.0” package in Suse:
New
Bug description:
Running smartgit 4.6.4 on 13.10 64 bits. After registering the
product, smartgit crash when trying to open a new repository. Java
error log :
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fa59061f9c0, pid=12494, tid=140349308167936
#
# JRE version: 7.0_25-b30
# Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64
compressed oops)
# Problematic frame:
# C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0
I tried different version of Java (Oracle v7 and v6 jre) with same
result. Also, Eclipse display blank menus so there's a general java
problem with displays.
To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
