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 654604 - audioringbuffer: Ring buffer race conition while activating causes critical
audioringbuffer: Ring buffer race conition while activating causes critical
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-07-14 10:51 UTC by Vincent Penquerc'h
Modified: 2014-11-25 17:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
log excerpt showing the two threads sliced at an inopportune time (2.34 KB, text/x-log)
2011-07-14 10:51 UTC, Vincent Penquerc'h
Details
stack trace and contents of buf (11.03 KB, application/octet-stream)
2011-07-14 10:53 UTC, Vincent Penquerc'h
Details

Description Vincent Penquerc'h 2011-07-14 10:51:49 UTC
Created attachment 191948 [details]
log excerpt showing the two threads sliced at an inopportune time

This seems to be a rare race condition, where a thread acquires a device, then another releases it, leaving the original thread left with a released device when it gets to using it.

I got it to happen twice when starting a call with meego-app-im and cancelling it quickly.
Comment 1 Vincent Penquerc'h 2011-07-14 10:53:01 UTC
Created attachment 191949 [details]
stack trace and contents of buf

Stack trace for the critical, with contents of buf printed at the end
Comment 2 Sebastian Dröge (slomo) 2014-02-08 15:31:40 UTC
Is this still a problem 2.5 years later?
Comment 3 Tim-Philipp Müller 2014-11-25 17:53:13 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!