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 778032 - race in gstclock detected by TSan
race in gstclock detected by TSan
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.10.x
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-02-01 14:19 UTC by Fabrice Bellet
Modified: 2018-11-03 12:39 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ThreadSanitizer: data race gstreamer/gst/gstclock.c:927 in gst_clock_adjust_unlocked (24.81 KB, text/plain)
2017-02-01 14:19 UTC, Fabrice Bellet 		Details

Description Fabrice Bellet 2017-02-01 14:19:22 UTC 
Created attachment 344711 [details]
ThreadSanitizer: data race gstreamer/gst/gstclock.c:927 in gst_clock_adjust_unlocked

ThreadSanitizer reports a race in gst_clock_adjust_unlocked(), because priv->last_time is written while being in a reader seqlock sequence in gst_clock_get_time()
Comment 1 Sebastian Dröge (slomo) 2017-02-01 17:31:35 UTC 
Indeed. Taking the write seqlock there would make that a bit awkward though, all main users of the seqlock would take the write version then... not sure how to best solve this.
Comment 2 GStreamer system administrator 2018-11-03 12:39:04 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer/issues/216.