← Back to team overview

touch-packages team mailing list archive

[Bug 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging

 

Launchpad has imported 40 comments from the remote bug at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=421073.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-11-05T14:49:18+00:00 Rulatir wrote:

Created attachment 237198
crash dump

This cripplingly frequent crash makes Kepler barely usable on this Arch
linux 64bit box. Ubuntu is apparently affected too:

https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181

Most recent dump attached.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/7

------------------------------------------------------------------------
On 2013-11-06T14:04:22+00:00 Adrian Woodhead wrote:

I can reliably reproduce this debugging applications on Kepler and
Kubuntu 13.04. I am happy to provide dumps or to try out possible fixes.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/8

------------------------------------------------------------------------
On 2013-11-19T14:02:35+00:00 Rulatir wrote:

Please everyone affected duly add votes for this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/12

------------------------------------------------------------------------
On 2013-12-06T09:54:43+00:00 Akurtakov wrote:

Can someone give a pure SWT reproducer? Does it happen with 4.4 M3 or if
you run SWT_GTK3=1 eclipse with Kepler?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/13

------------------------------------------------------------------------
On 2013-12-18T13:28:54+00:00 Akurtakov wrote:

We need help from reporters to investigate issues. If this doesn't
happen there is no other action to be done but to close it with
insufficient data.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/14

------------------------------------------------------------------------
On 2013-12-18T14:59:45+00:00 Adrian Woodhead wrote:

This stopped happening to me a week or two after reporting it. I had
tried changing my KDE theme as suggested in another report of this bug
(possibly on kde.org) and there had also been some Kubuntu updates which
I had applied. I am now using my original theme and the crash no longer
happens. I'm guessing some KDE update fixed it but I can't tell for
certain. I didn't change anything in Eclipse.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/15

------------------------------------------------------------------------
On 2013-12-30T00:43:51+00:00 Thomas Frühbeck wrote:

this crash started to plague me too, please continue work on this.
it happens, when i try to move mouse over Variables view during debugging. 
my system:
SuSE Linux 13.1
Linux 3.11.6-4-desktop #1 SMP PREEMPT (e6d4a27) x86_64 


Stack: [0x00007f728f199000,0x00007f728f29a000],  sp=0x00007f728f296a80,  free space=1014k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [libgtk-x11-2.0.so.0+0x22a52a]  gtk_tree_view_get_background_area+0x8a

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J  org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(J)V
J  org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(J)V
j  org.eclipse.swt.widgets.Display.eventProc(JJ)J+157
v  ~StubRoutines::call_stub
J  org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z
J  org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(JZ)Z
J  org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run()V

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/16

------------------------------------------------------------------------
On 2013-12-30T00:44:40+00:00 Thomas Frühbeck wrote:

Created attachment 238604
crash dump of VM

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/17

------------------------------------------------------------------------
On 2013-12-30T05:59:28+00:00 Akurtakov wrote:

(In reply to Thomas Frühbeck from comment #6)
> this crash started to plague me too, please continue work on this.
> it happens, when i try to move mouse over Variables view during debugging. 
> my system:
> SuSE Linux 13.1
> Linux 3.11.6-4-desktop #1 SMP PREEMPT (e6d4a27) x86_64 
> 
> 
> Stack: [0x00007f728f199000,0x00007f728f29a000],  sp=0x00007f728f296a80, 
> free space=1014k
> Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
> code)
> C  [libgtk-x11-2.0.so.0+0x22a52a]  gtk_tree_view_get_background_area+0x8a
> 
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> J  org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(J)V
> J  org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(J)V
> j  org.eclipse.swt.widgets.Display.eventProc(JJ)J+157
> v  ~StubRoutines::call_stub
> J  org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(JZ)Z
> J  org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(JZ)Z
> J  org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run()V

Thomas, what is your eclipse version? Have you tried running with GTK 3 as I asked for in comment 3? Can you come up with instructions how can I reliably reproduce? Any chance for pure SWT code reproducing the problem? 
I can not reproduce such a crash yet so unless someone comes with a reproducer I can not do much.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/18

------------------------------------------------------------------------
On 2014-01-05T16:54:04+00:00 Joerg-dippel wrote:

Kepler also crashes on a smaller Swing application while debugging.
I've set four breakpoints. On stepping through the program Kepler crashes.

I've used also SuSE 13.1: 
Linux 3.11.6-4-desktop #1 SMP PREEMPT (e6d4a27) x86_64

> rpm -qf /usr/lib64/libgtk-x11-2.0.so.0
libgtk-2_0-0-2.24.22-2.1.x86_64

eclipse.buildId=4.3.0.M20130911-1000

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/20

------------------------------------------------------------------------
On 2014-01-05T18:09:19+00:00 Akurtakov wrote:

(In reply to Jörg Dippel from comment #9)
> Kepler also crashes on a smaller Swing application while debugging.
> I've set four breakpoints. On stepping through the program Kepler crashes.
> 
> I've used also SuSE 13.1: 
> Linux 3.11.6-4-desktop #1 SMP PREEMPT (e6d4a27) x86_64
> 
> > rpm -qf /usr/lib64/libgtk-x11-2.0.so.0
> libgtk-2_0-0-2.24.22-2.1.x86_64
> 
> eclipse.buildId=4.3.0.M20130911-1000

Any chances for giving a snippet that reproduces the crash?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/21

------------------------------------------------------------------------
On 2014-01-05T20:04:09+00:00 Joerg-dippel wrote:

https://sourceforge.net/projects/chess383/files/Eclipse-421073-src.tar.gz/download

Eclipse seems to crash only on debugging, but that's not confirmed.
I've extracted some code to reproduce the behavior. The application is started by GameExample (that is in a state of refactoring), the relevant break point is set in BoardView, line 254.

The project is related to a Maven project (maybe the prefixes main/java
and test/java are to be removed and junit4 has to be added).

What should happen: On start a chess board is displayed, on next-Button
there should be changes on the chess board, which are not implemented
yet.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/22

------------------------------------------------------------------------
On 2014-01-08T08:44:09+00:00 Joerg-dippel wrote:

This performance (crashes on debugging) is annoying. I cannot remember
crashes on debugging while I get them often now.

The performance is repeatable on a fresh installed SuSE-13.1 with all updates available (from today).
If I use a SuSE-12.2 installation I cannot reproduce the crashes.

The SuSE-12.2 installation uses: 
> rpm -qf /usr/lib64//libgtk-x11-2.0.so.0
libgtk-2_0-0-2.24.10-3.1.2.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/23

------------------------------------------------------------------------
On 2014-01-19T04:23:43+00:00 NightStorm wrote:

I just upgraded from openSuSE 12.3 to 13.1 and now I am getting this
same crash, always during a Java debug session.  I never saw it in 12.3

Starting eclipse with "SWT_GTK3=1" gives me an unusable IDE (no source
text is drawn, lots of blank windows).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/24

------------------------------------------------------------------------
On 2014-01-19T18:19:22+00:00 Joerg-dippel wrote:

I can confirm that setting "SWT_GTK3=1" provides an unusable IDE.
First I get an "In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug" error", but after I set the ulimit command, I cannot reproduce that again.

But because I can reproduce the crash with my small project, I've tried
it nevertheless. The crash doesn't appear, but another problem occurs,
notified by a popup: Asynchronous viewer input update has encountered a
problem. An internal error has occurred. On details, only the number '4'
is returned.

Because I use Kepler with a former libgtk-x11-2.0.so.0, using 12.2, my
first candidate would be that library.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/25

------------------------------------------------------------------------
On 2014-01-19T19:24:44+00:00 NightStorm wrote:

I tried replacing the /usr/lib64/libgtk-x11-2.0.so.0.2400.22 with the
version from openSuSE 12.3 (libgtk-x11-2.0.so.0.2400.18), updating the
symlinks, and doing a full restart (just-in-case) but it made no
difference.  Still crashes.

I noticed that a crash is always after I bring the mouse into the
variables window during a debug. Not every entry into the variables
window results in a crash but the crash only occurs when I've done that.
I tried changing my focus policy from follows mouse to click-to-focus:
made no difference (still crashes).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/26

------------------------------------------------------------------------
On 2014-01-20T00:07:35+00:00 Joerg-dippel wrote:

Curious, I cannot reproduce this with two older 12.3 SuSEs, one Gnome
and the other LXDE, but both with the named lib
libgtk-x11-2.0.so.0.2400.18.

My crash happens on KDE. Thus I've installed a 13.1 LXDE with all updates and there is no crash.
Back to 13.1 KDE the crash can be repeated.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/27

------------------------------------------------------------------------
On 2014-01-20T06:57:14+00:00 Akurtakov wrote:

(In reply to Jörg Dippel from comment #16)
> Curious, I cannot reproduce this with two older 12.3 SuSEs, one Gnome and
> the other LXDE, but both with the named lib libgtk-x11-2.0.so.0.2400.18.
> 
> My crash happens on KDE. Thus I've installed a 13.1 LXDE with all updates
> and there is no crash.
> Back to 13.1 KDE the crash can be repeated.

This reminds me of a series of bug with oxygen-gtk theme. Is this what
you use on KDE? Can you try changing the gtk theme from KDE settings?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/28

------------------------------------------------------------------------
On 2014-01-20T15:44:45+00:00 Joerg-dippel wrote:

I take the default - this is KDE Plasma Desktop. Normally I only need an
xterm ...

Executing ps -ef, I get 'kdeinit4: plasma-desktop [kdeinit]'.
In KDE System Settings->Application Appearance->GTK Styles and Fonts the GTK-Style is set to 'oxygen-gtk' for GTK2.

If I choose another predefined selection for GTK2 like Adwaita I can no
longer reproduce the crash, going back to oxygen-gtk the crash can be
reproduced again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/29

------------------------------------------------------------------------
On 2014-01-20T15:51:16+00:00 Akurtakov wrote:

(In reply to Jörg Dippel from comment #18)
> I take the default - this is KDE Plasma Desktop. Normally I only need an
> xterm ...
> 
> Executing ps -ef, I get 'kdeinit4: plasma-desktop [kdeinit]'.
> In KDE System Settings->Application Appearance->GTK Styles and Fonts the
> GTK-Style is set to 'oxygen-gtk' for GTK2.
> 
> If I choose another predefined selection for GTK2 like Adwaita I can no
> longer reproduce the crash, going back to oxygen-gtk the crash can be
> reproduced again.

I myself consider this as bug in oxygen-gtk too. Even if SWT is doing
something weird a theme should not crash gtk applications. This doesn't
mean SWT part of the problem shouldn't be looked at but SWT is pretty
low on resources now. So if you can either help oxygen-gtk or swt
projects it would be more than welcome.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/30

------------------------------------------------------------------------
On 2014-01-28T05:32:21+00:00 Aurik94 wrote:

I'm seeing this same bug as well on Fedora 20.  It has crashed on me 5
times in the past hour.  The most recent gave me the following error:

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000003cf36570c2, pid=16843, tid=140722662307584
#
# JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_17_13_38-b00)
# Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgtk-x11-2.0.so.0+0x2570c2]  gtk_tree_view_get_background_area+0xb2
#
# Core dump written. Default location: /home/ken/eclipse/core or core.16843
#
# An error report file with more information is saved as:
# /tmp/jvm-16843/hs_error.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
#   http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

The past few times it has occurred to me was when I was attempting to
step through some Java code in the Debug view.  I can attach the code
I'm trying to debug if that would help.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/31

------------------------------------------------------------------------
On 2014-02-26T19:30:26+00:00 Alcocerpi wrote:

Created attachment 240341
hs_err_pid32677 error log

Frequent crashes when viewing variables in the debugger. I am running
Fedora 20 and Keplar 64 bit.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/33

------------------------------------------------------------------------
On 2014-03-05T09:55:04+00:00 Adrian Woodhead wrote:

Created attachment 240533
Attached full crash log

Eclipse crashes frequently in debug mode, no exact steps to reproduce
but happens within minutes of debugging. Seems to be happening now in

libgtk-x11-2.0.so.0+0x2202aa

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/34

------------------------------------------------------------------------
On 2014-03-20T22:13:35+00:00 Joerg-dippel wrote:

Today there has been an updated package for oxygen theme gtk2-theme-oxygen-1.4.4-2.4.1.x86_64 for SuSE 13.1.
Because my installed package for 

> rpm -qi libgtk-2_0-0-2.24.22-2.1.x86_64
Name        : libgtk-2_0-0
Version     : 2.24.22
Release     : 2.1
Architecture: x86_64
Install Date: Mi 06 Nov 2013 21:01:02 CET
Build Date  : Fr 01 Nov 2013 12:07:48 CET

has not changed, the crash should be reproduced again.
The crash can be reproduced with GTK-Design oxygen-gtk with the currently updated system.

With a change of GTK design there is no crash - that's my workaround.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/35

------------------------------------------------------------------------
On 2014-04-15T10:49:03+00:00 David Matějček wrote:

(In reply to Mass Dosage from comment #22)
> Created attachment 240533 [details]
> Attached full crash log
> 
> Eclipse crashes frequently in debug mode, no exact steps to reproduce but
> happens within minutes of debugging. Seems to be happening now in 
> 
> libgtk-x11-2.0.so.0+0x2202aa

Exactly, I can confirm this information.
Also Java Perspective crashes when drawing some background, but it is not so early.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/37

------------------------------------------------------------------------
On 2014-04-15T20:00:06+00:00 David Matějček wrote:

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 (9 hours now,
switching git branches on massive project, debugging, refactoring).

Can you try it someone too? (package is big, you need fast connection)
sudo add-apt-repository ppa:gnome3-team/gnome3
sudo apt-get install libgtk-3-0
Download 1.3.5: https://launchpad.net/ubuntu/+source/oxygen-gtk3
Unpack and see instructions in the file INSTALL.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/38

------------------------------------------------------------------------
On 2014-04-18T15:58:35+00:00 Ken Corbin wrote:

This used to be incredibly annoying, to the point of making debugging
unusable, until I discovered a simple workaround.  The crash almost
always happens when you move the mouse into the left edge of the
variables view.  Where you have to go to expand or compress tree nodes
in the variable display.  Moving the mouse into this area is extremely
dangerous, I was averaging about one crash for every 4 times I tried to
expand a variable node.

Then, I discovered you could expand or unexpand variable nodes by double
clicking the node in the center of the variable view.  Since I no longer
have to move into the dangerous left edge of the variable view, eclipse
has been almost problem free.

This isn't a perfect answer.  The crash still does happen at seemingly
random when I move the mouse in the Java perspective.  But this only
happens once every couple weeks.  I can live with that.

Eclipse version: Kepler Service Release 1
Build id: 20139019-8919
OS: OpenSuse 13.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/39

------------------------------------------------------------------------
On 2014-05-13T15:47:37+00:00 Stephan-herrmann wrote:

Also happens with brand new Kubuntu 14.04 LTS

Eclipse version: Kepler SR1 + J8
Using gtk2 with oxygen-gtk
   (since Eclipse on gtk3 isn't usable at all on this box).

Most likely related to the Variables view, too.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/40

------------------------------------------------------------------------
On 2014-05-20T15:06:52+00:00 F-laza-rabearisoa wrote:

Installing Oracle Java JDK on Kubuntu Linux 14.04 LTS (x86_64) seems to
work with eclipse kepler (4.3.2) downloaded and installed directly from
eclipse site instead of using the kubuntu repositories :

You download the eclipse .tar.gz package and install eclipse like below (all instructions preceded with sudo, of course) 
mv /Downloads/eclipse /opt
ln -s /opt/eclipse/eclipse /usr/local/bin/eclipse
cd /opt
chown -R root:root eclipse
chmod -R g-w eclipse


Then, you can find how to perform Oracle JDK installation here : http://www.wikihow.com/Install-Oracle-Java-JDK-on-Ubuntu-Linux

Let me know if it works please.

Regards.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/41

------------------------------------------------------------------------
On 2014-05-20T15:29:35+00:00 Stephan-herrmann wrote:

(In reply to lazare lazare from comment #28)

Thanks for the hint!

What you describe is pretty much the setup I use all the time (except I install everything as a regular user, into a place where I have the permission).
BUT when I reported comment 27 I was indeed using /usr/bin/java, which identifies itself as

java version "1.7.0_55"
OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1)
OpenJDK Server VM (build 24.51-b03, mixed mode)

Going back to an original jdk (1.8.0 in my case) seems to fix this issue for me.
Thanks again.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/42

------------------------------------------------------------------------
On 2014-05-21T13:01:35+00:00 F-laza-rabearisoa wrote:

My problem is unfortunately not yet solved even though the crash occurs
a little less frequently.

Debugging becomes a tedious task as often having arrived at a breakpoint
, simply move the mouse over the window without clicking anything is
enough to cause the crash.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/43

------------------------------------------------------------------------
On 2014-05-21T14:28:58+00:00 Dan wrote:

In case people aren't aware, the workaround for this bug is to go to
System Settings -> Appliation Appearance -> GTK

And then change the GTK2 theme from 'oxygen-gtk' to something else.

I've been using Clearlooks myself, and it completely eliminates the bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/44

------------------------------------------------------------------------
On 2014-05-21T16:25:33+00:00 F-laza-rabearisoa wrote:

Great ! Thanks a lot. I'd never have guessed it.

I hope it fixes the problem for good.(In reply to Daniel Armbrust from
comment #31)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/45

------------------------------------------------------------------------
On 2014-05-21T21:02:42+00:00 Stephan-herrmann wrote:

With all the suggestions about themes: is anybody on this bug aware of a
working gtk3 theme that is suitable for KDE? I'm primarily concerned
about the button order, which seems to be defined by the theme.

E.g., on KDE the correct order for a standard dialog is

  [ OK ] [ Cancel ]

With unthemed GTK3 as well as themes like Clearlooks it's:

  [ Cancel ] [ OK ]

which is like driving on the left side of the road :)
and will be responsible for many accidents...


So far, oxygen-gtk is the *only* correct gtk3 theme for KDE in this regard, that I've come across. Any hints?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/46

------------------------------------------------------------------------
On 2014-05-22T02:39:30+00:00 Marc-andre-laperle wrote:

(In reply to Stephan Herrmann from comment #27)
> Also happens with brand new Kubuntu 14.04 LTS
> 
> Eclipse version: Kepler SR1 + J8
> Using gtk2 with oxygen-gtk
>    (since Eclipse on gtk3 isn't usable at all on this box).
> 
> Most likely related to the Variables view, too.

I tried to reproduce this crash with no success.
Ubuntu 14.04
KDE plasma desktop + oxygen-gtk
both Kepler SR2 and Luna I20140512-2000
both OpenJDK 1.7.0_55 and Oracle Java 1.8.0_05
I'm using GTK2

I'm debugging code in ToolItem.java (SWT) and clicking in the Variables
view as a test.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/47

------------------------------------------------------------------------
On 2014-05-22T02:41:07+00:00 Marc-andre-laperle wrote:

Created attachment 243376
Variables view screenshot

This is what my variables view looks like. I'm not that familiar with
KDE and its themes so let me know if this looks wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/48

------------------------------------------------------------------------
On 2014-05-22T17:51:13+00:00 Stephan-herrmann wrote:

(In reply to Marc-Andre Laperle from comment #34)
(In reply to Marc-Andre Laperle from comment #35)
> Created attachment 243376 [details]
> Variables view screenshot
> 
> This is what my variables view looks like. I'm not that familiar with KDE
> and its themes so let me know if this looks wrong.

Thanks for trying.

Looks familiar to me :)

The Kubuntu 14.04 box is not my primary machine, and since avoiding the
ubuntu-version of of OpenJDK I have not again seen the crash. But so far
I have too little data to draw any conclusions from.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/49

------------------------------------------------------------------------
On 2014-07-02T01:53:09+00:00 Arcadiy wrote:

Posting core file and hs_err as well. The issue started occurring
recently on Fedora 20.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/50

------------------------------------------------------------------------
On 2014-07-02T21:23:16+00:00 Arcadiy wrote:

Unable to upload a 200mb crash dump, here's the link: http://public-bug-
report-attachments.s3-website-us-
east-1.amazonaws.com/hs_err_pid88816.tar.gz

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/51

------------------------------------------------------------------------
On 2014-07-23T17:54:03+00:00 Arunkumar-thondapu-i wrote:

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/comments/52


** Changed in: eclipse
       Status: Unknown => Confirmed

** Changed in: eclipse
   Importance: Unknown => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1223181

Title:
  After upgrading to saucy, eclipse crashes in
  gtk_tree_view_get_background_area+0x8a while debugging

Status in Eclipse:
  Confirmed
Status in GTK+ GUI Toolkit:
  Unknown
Status in “gtk+2.0” package in Ubuntu:
  Confirmed

Bug description:
  to reproduce, I open the "Variables" view in eclipse and step through
  the application. the eclipse jvm crashes with:

  #
  # A fatal error has been detected by the Java Runtime Environment:
  #
  #  SIGSEGV (0xb) at pc=0x00007f3dea4082aa, pid=11567, tid=139905336198912
  #
  # JRE version: 7.0_21-b11
  # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops)
  # Problematic frame:
  # C  [libgtk-x11-2.0.so.0+0x2202aa]  gtk_tree_view_get_background_area+0x8a
  #
  # Core dump written. Default location: /home/juergen/core or core.11567
  #
  # An error report file with more information is saved as:
  # /home/juergen/hs_err_pid11567.log
  #
  # If you would like to submit a bug report, please visit:
  #   http://bugreport.sun.com/bugreport/crash.jsp
  # The crash happened outside the Java Virtual Machine in native code.
  # See problematic frame for where to report the bug.
  #

  This did not happen in ubuntu 13.04.

  using KDE as a desktop (installed ubuntu, installed kde packages)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Tue Sep 10 07:25:17 2013
  InstallationDate: Installed on 2010-11-24 (1020 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eclipse/+bug/1223181/+subscriptions