Bug 614719 – banshee crashes on exit when Alarm Clock extension is enabled

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 614719 - banshee crashes on exit when Alarm Clock extension is enabled


Summary:	banshee crashes on exit when Alarm Clock extension is enabled


Status:	RESOLVED FIXED

Product:	banshee
Classification:	Other
Component:	Community Extensions
Version:	1.6.0
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	1.x
Assigned To:	Banshee Maintainers
QA Contact:	Banshee Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-04-03 09:02 UTC by Christian Krause
Modified:	2010-11-05 00:39 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
debug output and full backtrace (13.63 KB, text/plain) 2010-04-03 09:02 UTC, Christian Krause	Details

Description Christian Krause 2010-04-03 09:02:20 UTC

Created attachment 157790 [details]
debug output and full backtrace

Banshee crashes on exit when Alarm extension is enabled:

- install banshee-community-extensions
- disable all extensions in Banshee besides Alarm Clock
- start Banshee with "banshee-1 --debug"

banshee crashes:

+ Trace 221222

Thread 1 (Thread 0xa2c6f0 (LWP 7509))

#0 __kernel_vsyscall
#1 read
at ../sysdeps/unix/syscall-template.S line 82
#2 read
at /usr/include/bits/unistd.h line 45
#3 mono_handle_native_sigsegv
at mini-exceptions.c line 1809
#4 mono_arch_handle_altstack_exception
at exceptions-x86.c line 905
#5 <signal handler called>
#6 __pthread_kill
at ../nptl/sysdeps/unix/sysv/linux/pthread_kill.c line 43
#7 GC_suspend_all
at pthread_stop_world.c line 341
#8 pthread_stop_world
at pthread_stop_world.c line 369
#9 GC_stop_world
at pthread_stop_world.c line 434
#10 GC_stopped_mark
at alloc.c line 503
#11 GC_try_to_collect_inner
at alloc.c line 382
#12 GC_try_to_collect
at alloc.c line 809
#13 GC_gcollect
at alloc.c line 822
#14 mono_domain_finalize
at gc.c line 352


I have attached the full debug output and backtrace.

Since the crash happens always after "[1 Debug 10:53:36.716] Service disposed (DbConnection)" I'm not 100% sure whether it is really a problem in the Alarm Clock extensions, but it is quite consistent that it happens only if it is enabled.

Comment 1 Bertrand Lorentz 2010-04-03 09:54:18 UTC

Things haven't changed much in the Alarm extensions for quite a while. But maybe there's a race condition that you're hitting.

Which version of mono do you have on your system ?

Comment 2 Christian Krause 2010-04-04 17:15:41 UTC

(In reply to comment #1)
> Which version of mono do you have on your system ?

mono-core-2.6.1-2.fc13.i686

Comment 3 Bertrand Lorentz 2010-08-13 15:29:54 UTC

After looking at the log, it looks like a bug in your version of mono, probably triggered by the AlarmClock extension.

If mono was updated on your system since you noticed the problem, could you try to reproduce it again ?

Comment 4 Christian Krause 2010-08-14 15:24:13 UTC

The problem still happens with mono 2.6.4, banshee 1.6.1.

On my system I can reproduce it quite easily if I close banshee while playing a song (and having the Alarm Clock extension enabled).

Comment 5 Bertrand Lorentz 2010-09-17 18:48:26 UTC

I wasn't able to reproduce the problem (on mono 2.6.7), but I just committed a small change that might fix this : the alarm extension now ensures the alarm thread has terminated while disposing.

Could you try to reproduce the problem with the latest AlarmClock extension from git master ?

Comment 6 Felipe Besoaín Pino 2010-11-02 01:50:49 UTC

Christian could you please try the comment 5?
thanks

Comment 7 Christian Krause 2010-11-05 00:09:55 UTC

I have tested banshee-1.8.0 which contains the fix and I couldn't reproduce the problem anymore. Thanks!