GNOME Bugzilla – Bug 787431
gstaudioringbuffer: should not be reached critical
Last modified: 2018-01-19 18:25:52 UTC
hi. i'm facing a gst critical: i'm trying one and the same pipeline on two different pcs. they both run the same ubuntu linux 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux i'm executing this pipeline: gst-launch-1.0 filesrc location="myfile.mp4" ! decodebin name=mux ! fakesink mux. ! audioconvert ! alsasink on one system it runs fine. on the other one it causes this message: CRITICAL **: file gstaudioringbuffer.c: line 1971 (gst_audio_ring_buffer_set_channel_positions): should not be reached do you have any information what might cause this message and how i could avoid or detect it? if you need further information please let me know. the file causing this critical message is attached. best, henning
Created attachment 359390 [details] file causing the above described critical output
I can't reproduce the warning here with the tip of the 1.8, 1.10 or 1.12 branches, but it does look familiar, so it may well have been fixed already. It might be a related to bug #763799 (which was fixed in 1.10), although I don't see the case from that bug (channels without position) in your file, so maybe it's not related after all. Any chance you could try with a more recent GStreamer version?
Can't really do anything about this without more information, sorry. Please feel free to re-open if it still happens with recent versions of GStreamer (>= 1.12.x) and you can provide: - a stack trace of the critical (run with G_DEBUG=fatal_warnings) - a GST_DEBUG=*:6 log up to the warning (run with G_DEBUG=fatal_warnings GST_DEBUG=*:6)