[Dx-packages] [Bug 1241101]

2014-04-16 Thread David Matějček
It seems it is fixed in newer GTK, but after my recent experiences I am not so optimistic. But after upgrade to 1.3.5 and also GTK 3.10 and restarting the system Eclipse still did not crash (10 hours yesterday, 5 hours today, switching git branches on massive project, debugging, refactoring). Can

[Dx-packages] [Bug 1241101]

2014-04-15 Thread David Matějček
EDIT: workaround does not help. And one more note: Eclipse crashes earlier when showing variables in debug mode. -- 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/bu

[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-15 Thread David Matějček
Yes, today Eclipse crashes again, taskset does not help. :( This is really very bad, hardly reproducible bug. It seems the faster machine and newer JDK and Linux, the more occurences I have ... Maybe the fastest method to fix it is to dig into the code of GTK ...? -- You received this bug notifi

[Dx-packages] [Bug 1241101]

2014-04-10 Thread David Matějček
Workaround: 1) Start the Eclipse 2) find pid of the process 3) taskset -p 0x0001 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 ...

[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-10 Thread David Matějček
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 0x0001 The problem is something

[Dx-packages] [Bug 1241101]

2014-04-10 Thread David Matějček
Reproduced also with the JDK6, OpenJDK7, and finally JDK8: Java(TM) SE Runtime Environment (build 1.8.0-b132) Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) Problematic frames occurs in two variants: 1) # C [libgobject-2.0.so.0+0x31b3c] g_type_check_instance_is_a+0x3c 2) # C [li

[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-10 Thread David Matějček
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 somet

[Dx-packages] [Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-10 Thread David Matějček
Reproduced also with the JDK6, OpenJDK7, and finally JDK8: Java(TM) SE Runtime Environment (build 1.8.0-b132) Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) Problematic frames occurs in two variants: 1) # C [libgobject-2.0.so.0+0x31b3c] g_type_check_instance_is_a+0x3c 2) # C [li