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 744085 - pulsesrc: criticals with very large latency-time values
pulsesrc: criticals with very large latency-time values
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal minor
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-02-06 08:57 UTC by Tim-Philipp Müller
Modified: 2018-01-22 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2015-02-06 08:57:00 UTC 
gst-launch-1.0 pulsesrc latency-time=1000000000 ! fakesinkSetting pipeline to PLAYING ...

** (gst-launch-1.0:14896): CRITICAL **: gst_audio_format_fill_silence: assertion 'dest != NULL' failed
New clock: GstPulseSrcClock

** (gst-launch-1.0:14896): CRITICAL **: gst_audio_ring_buffer_read: assertion 'buf->memory != NULL' failed

(Yes, I realise latency-time is not in nanoseconds, still..)
Comment 1 Nicolas Dufresne (ndufresne) 2015-02-06 13:30:50 UTC 
Might be wrong, but I thought this assert was popping when latency-time is bigger (or not a multiple) or buffer-time, could that be ? (also seen on another source)
Comment 2 Tim-Philipp Müller 2018-01-22 11:53:01 UTC 
Doesn't seem to happen any more.