GNOME Bugzilla – Bug 166917
deadlock in queue
Last modified: 2005-02-16 03:19:02 UTC
Here's a deadlock scenario I keep encountering in totem. It's happening a lot because of the high rate navigation events, I think. Particularly, note that both thread 1 and thread 2 are waiting on the item_add for the same queue, one sending a src_event and one calling _get. I don't know how that happens other than a bug in opt? (gdb) thread 1 [Switching to thread 1 (Thread -1224661536 (LWP 4379))]#0 0xffffe410 in ?? () (gdb) bt
+ Trace 55546
Created attachment 37458 [details] [review] Add locking and queueing of navigation events in xvimagesink so, this would seem to be because totem sends mouse movements from the main thread and they get forwarded upstream. Attaching a patch to add locking and defer sending the navigation events until the next call to the chain function. Patch for ximagesink soon
Created attachment 37459 [details] [review] same patch for ximagesink
for the bug history, a symptom was also random crashes in the queue src event handling from the same cause. Also appears fixed by these patches.
Committed.