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 549012 - deadlock in DAP
deadlock in DAP
Status: RESOLVED DUPLICATE of bug 614039
Product: banshee
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-22 15:05 UTC by James Willcox
Modified: 2010-11-26 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Banshee log, includes thread trace (41.37 KB, text/plain)
2008-08-22 15:06 UTC, James Willcox 		Details

Description James Willcox 2008-08-22 15:05:46 UTC 
I got up this morning to find Banshee unresponsive, so I looked into what might
be causing it.  It appears that there is a deadlock in DAP caused by a dbus
call not returning.  I'll attach the log which includes a thread trace.  I am
running Banshee from subversion, r4410.
Comment 1 James Willcox 2008-08-22 15:06:17 UTC 
Created attachment 117226 [details]
Banshee log, includes thread trace
Comment 2 James Willcox 2008-08-22 15:07:07 UTC 
There are two threads attempting to hold the Banshee.Dap.DapService.sync lock. 
The thread which obtained the lock is blocked while waiting on a dbus reply --
line 331.  The second thread (which is the main UI thread) is waiting for the
same lock on line 272.

It appears that the locking is maybe a little overzealous, but I think the root
cause is that the dbus call just blocked forever.  It smells like a bug in
dbus-sharp -- either it dropped the reply, or did not properly time out.
Comment 3 James Willcox 2008-08-22 15:07:51 UTC 
Oh, I forgot to mention that when I sent the SIGQUIT to get the stack traces,
it freed things up somehow.  I'd imagine it's just a side effect of the
fetching the traces, but I don't know.
Comment 4 David Nielsen 2010-11-26 18:56:54 UTC 
I am pretty sure this is the same bug as https://bugzilla.gnome.org/show_bug.cgi?id=614039 at it's core, however the newer bug has more information on it's eventual fix so I am marking this as the duplicate.

*** This bug has been marked as a duplicate of bug 614039 ***