Bug 1045873

Created attachment 840381 [details]
File: backtrace

Created attachment 840382 [details]
File: cgroup

Created attachment 840383 [details]
File: core_backtrace

Created attachment 840384 [details]
File: dso_list

Created attachment 840385 [details]
File: environ

Created attachment 840386 [details]
File: hs_err.log

Created attachment 840387 [details]
File: limits

Created attachment 840388 [details]
File: maps

Created attachment 840389 [details]
File: open_fds

Created attachment 840390 [details]
File: proc_pid_status

Created attachment 840391 [details]
File: var_log_messages

Another user experienced a similar problem:

Stitching images to panorama. Kipi Panorama Creator wizard asks for file name to save. Click Finish and boom. Image is saved but /tmp is not cleaned up

reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        eclipse
crash_function: signalHandler
executable:     /usr/lib/eclipse/eclipse
kernel:         3.12.5-302.fc20.i686+PAE
package:        eclipse-platform-4.3.1-11.fc20
reason:         eclipse killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Debugging android app. When breakpoint was reached, pressed step over and boom

reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        /usr/bin/eclipse
crash_function: signalHandler
executable:     /usr/lib/eclipse/eclipse
kernel:         3.12.5-302.fc20.i686+PAE
package:        eclipse-platform-4.3.1-11.fc20
reason:         eclipse killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Debugging android app running in emulator. Pressed step over and crash. This happen very often since I upgraded to FC20. Already tried reinstalling eclipse and removing .eclipse. Also installed eclipse from eclipse.org, same problem

reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        /usr/bin/eclipse
crash_function: signalHandler
executable:     /usr/lib/eclipse/eclipse
kernel:         3.12.6-300.fc20.i686+PAE
package:        eclipse-platform-4.3.1-11.fc20
reason:         eclipse killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Working on Android project. Edited a .xml resource in graphical editor ctrl-s and navigate to .java tab

reporter:       libreport-2.1.10
backtrace_rating: 3
cmdline:        eclipse
crash_function: signalHandler
executable:     /usr/lib/eclipse/eclipse
kernel:         3.12.6-300.fc20.i686+PAE
package:        eclipse-platform-4.3.1-11.fc20
reason:         eclipse killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

There were problems reported in the past about oxygen gtk theme causing crashes. Would you please try whether using other gtk theme causes it ?

I was using the Heisenbug theme. I now switched to Schrodinger's Cat because on FC19 I did not have these eclipse crashes. Will let you know. One thing I find strange is that if I download eclipse from eclipse.org that version also crashes but not as often.

Have been working with the Schrodinger's Cat theme now for a couple of days.
As long as I don't debug my app everything is fine. When debugging app stops on a breakpoint, eclipse switches to sourcefile fine. Then when I press e.g. step over eclipse almost always crashes. (If not the first time, it crashes the second time I start my app in debugging mode).

Sorry, just realized that I only changed the kde theme. Just changed the GTK+ appearance in system settings and now the crash seems to have disappeared. Will continue testing tomorrow

(In reply to Alexander Kurtakov from comment #16)
> There were problems reported in the past about oxygen gtk theme causing
> crashes. Would you please try whether using other gtk theme causes it ?

Definitely the oxygen theme. I've been debugging the entire day and not a single crash using the Glossy theme.

Reassigning to oxygen-gtk2 as the crash happens only with this theme.

I suspect this is similar to:
https://bugs.kde.org/show_bug.cgi?id=326424
https://bugzilla.gnome.org/show_bug.cgi?id=729651

workaround in the meantime is to edit
/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc
and set
GtkComboBox::appears-as-list = 0

Here's a set of bugs that are eclipse specific fwiw
https://bugs.kde.org/show_bug.cgi?id=329814
https://bugzilla.gnome.org/show_bug.cgi?id=736323

And now full circle,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=372560

and eclipse fix/workaround,
http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=19969099fb0b8b88c03bc7dc1b553ccf865db827

Re-assigning (back) to eclipse, to see if the choose to pull in the fix or not.  else, we can consider including the workaround in oxygen-gtk2 (or wait for gtk2 to be fixed)

(In reply to Rex Dieter from comment #25)
> Re-assigning (back) to eclipse, to see if the choose to pull in the fix or
> not.  else, we can consider including the workaround in oxygen-gtk2 (or wait
> for gtk2 to be fixed)

The patch has been applied in 4.3 which we ship in Fedora 20 so it's not the fix needed.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.