[Bug 762552] Crash on repeated pipeline, bus and signal watch creation

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Tue Nov 15 22:30:52 UTC 2016


https://bugzilla.gnome.org/show_bug.cgi?id=762552

--- Comment #26 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
I actually made a mistake debugging this. It is the g_source_attach that keeps
a reference on the gsource, but the rest holds true.

Using g_source_destroy fixes the rtsp tests but breaks pipelines/gio in -base.
It tries to do a g_source_remove after the bus has been destroyed. Not sure
this is a valid usecase. Should users expect the GSource to outlive the GstBus?

"gstcheck.c:79:F:general:test_memory_stream:0: Unexpected critical/warning:
Source ID 1 was not found when attempting to remove it"

I start to wonder if we are not creating more holes by fixing this and should
just tell users to properly clean up the watches after they are not needed
anymore.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list