GNOME Bugzilla – Bug 785714
gst_poll_read_control: assertion 'set != NULL' failed when running many pipelines one after another
Last modified: 2017-08-03 08:01:32 UTC
Created attachment 356759 [details]
Reproduces the reported issue
Building and running the attached program with an image as the URI (so that the pipelines end as fast as possible) should eventually reproduce the issue, not sure what's happening but it's pretty bad, I'll attach a stacktrace to show where the assertion pops
Created attachment 356760 [details]
Trace obtained with G_DEBUG=fatal-criticals gdb --args ./build/subprojects/gst-plugins-bad/tools/mosaic_db/make_mosaic_db file:///usr/share/shotwell/icons/shotwell-street.jpg
This is probably caused by something leaking file descriptors. You're leaking for example the bus in your testcase, which owns a file descriptor. And possibly the bus watch.
Does that solve it?
The bus is an autptr, it's not leaked. But to be safe, just run with the leak tracer.
Perhaps check the file descriptor thesis by running lsof -p $PID regularly and see if the number increases or not.
And that's exactly why g_autoptr is not a good idea ;)
Try removing the bus watch nonetheless.
> Try removing the bus watch nonetheless.
Thanks, that was the issue, sorry about the noise :)
*** This bug has been marked as a duplicate of bug 762552 ***