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 702426 - deadlock : timelinepipeline lock dyn vs timeline lock dyn
deadlock : timelinepipeline lock dyn vs timeline lock dyn
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-editing-services
git master
Other Linux
: Normal normal
: 1.2.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-06-17 07:46 UTC by Alban Browaeys
Modified: 2013-11-16 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdb backtrace : deadlock : timelinepipeline lock dyn vs timeline lock dyn (35.39 KB, text/plain)
2013-06-17 07:46 UTC, Alban Browaeys 		Details

Description Alban Browaeys 2013-06-17 07:46:17 UTC 
Created attachment 247002 [details]
gdb backtrace : deadlock : timelinepipeline lock dyn vs timeline lock dyn

ges timeline pad_added_cb (lock timeline) call ges timeline pipeline no_more_pad (lock timelinepipeline)      
VS
ges timeline pipeline pad_removed_cb (lock timelinepipeline) call ges_timeline_get_track_for_pad (lock timeline)
leads to deadlock
Comment 1 Thibault Saunier 2013-11-16 22:56:00 UTC 
commit 0c871049553ca2d649c9aceae04123aea3f6d36e
Author: Thibault Saunier <thibault.saunier@collabora.com>
Date:   Mon Aug 19 15:13:48 2013 -0400

    pipeline: Remove the dynamic lock
    
    We actually do not need it has everywhere where we would need it we are
    already locked against the timeline.dyn_lock, we need to make sure it is
    always the case in the future.
    
    The hierarchy of the mutex was wrong and could possibly lead to
    deadlocks