After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621597 - f-spot crashes on exit
f-spot crashes on exit
Status: RESOLVED FIXED
Product: f-spot
Classification: Other
Component: General
0.6.2
Other Linux
: Normal major
: 0.7.0
Assigned To: F-spot maintainers
F-spot maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-14 22:44 UTC by Christian Krause
Modified: 2010-06-16 12:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
output of f-spot including backtrace (15.13 KB, text/plain)
2010-06-14 22:44 UTC, Christian Krause
Details

Description Christian Krause 2010-06-14 22:44:18 UTC
Created attachment 163641 [details]
output of f-spot including backtrace

F-Spot 0.6.2 crashes very frequently on exit. It is not 100% reproducible, but I see the problem probably in 20% of the tests.

How to reproduce:
- open f-spot
- just use it (the following steps may help to reproduce the issue)
* scroll in the browse view
* double click one picture
- exit f-spot (e.g. using the "X" button of the f-spot window)

The same issue was also reported by some f-spot users in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=596601

According to the output during the crash the problem may be related to threads:

ERROR:threads.c:1099:ves_icall_System_Threading_Thread_Thread_free_internal: assertion failed: (!this->abort_exc && !this->abort_state_handle)
Stacktrace:

  at (wrapper managed-to-native) System.Threading.Thread.Thread_free_internal (intptr) <0x00004>
  at (wrapper managed-to-native) System.Threading.Thread.Thread_free_internal (intptr) <0x00004>
  at System.Threading.Thread.Finalize () <0x00017>
  at (wrapper runtime-invoke) object.runtime_invoke_virtual_void__this__ (object,intptr,intptr,intptr) <0x00046>

I have attached the full output of f-spot (including the backtrace) when the problem occurs.

Please also note, that it looks like that this issue got introduced with 0.6.2. I have not seen it before (or it happened with a much less frequency).
Comment 1 Ruben Vermeersch 2010-06-16 12:58:30 UTC
I think I've tracked this down, should be fixed now.

commit 993721a795dcd7d37beb136fb54eb5bb9aa59a6c
Author: Ruben Vermeersch <ruben@savanne.be>
Date:   Wed Jun 16 14:56:21 2010 +0200

    Don't crash on exit due to thread abortion.