dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #13258
[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
I have an idea, theoretical scenario: isn't it somehow similar problem as with the volatile and synchronization in Java?
GTK makes many updates and redrawing at the same time.
Even Eclipse have parallel threads for redrawing.
I got 2core/4thread CPU Intel i5.
What if the GTK tries to redraw something, but the CPU context switching occurs and then it has invalid references?
All code then seems correct, but it is not.
I see these crashes for maybe two years (perhaps since Kubuntu 12.10),
some were closed as incomplete, one even as fixed (bug in intel driver),
but this problem is still the same.
Maybe I will try some experiments with the affinity and I will see if it will make some difference:
http://karuppuswamy.com/wordpress/2010/09/23/how-to-launch-your-application-in-a-specific-cpu-cpu-affinity-in-linux/
--
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