[Bug 746541] glimagesink memleak

[GStreamer (GNOME Bugzilla)]

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

--- Comment #4 from Julien Isorce <julien.isorce at gmail.com> ---
Ah sorry I missed this part.
I made a quick investigation, breaking on gst_gl_context_create then on
g_thread_new then g_slice_alloc0 provides the following backtrace:

#0  0x00000001002476ba in g_slice_alloc0 ()
#1  0x000000010026bb91 in g_system_thread_new ()
#2  0x0000000100250de5 in g_thread_new_internal ()
#3  0x0000000100250d6f in g_thread_new ()
#4  0x00000001019a83c3 in gst_gl_context_create (context=0x1010c9090,
other_context=0x0, error=0x1050aa7b0) at gstglcontext.c:928
#5  0x000000010194dad6 in _ensure_gl_setup (gl_sink=0x1008a6e10) at
gstglimagesink.c:744
#6  0x000000010194c5f2 in gst_glimage_sink_set_caps (bsink=0x1008a6e10,
caps=0x101072230) at gstglimagesink.c:1088
#7  0x000000010182f4b0 in gst_base_sink_default_event (basesink=0x1008a6e10,
event=0x1008ae260) at gstbasesink.c:3083

Which matches what valgrind gave you (+ the 2 missing ???,
g_thread_new_internal and g_system_thread_new)

Then the g_slice_alloc0 seems to be the "g_slice_new0 (GThreadPosix)" here
https://git.gnome.org/browse/glib/tree/glib/gthread-posix.c?h=glib-2-42#n1154

And we join the thread in gst_gl_context_finalize we should unref it
internally: "g_thread_join() consumes the reference to the passed-in thread"

I have not valgrind with macports since I upgraded to osx 10.10.

If you find more infos please open a new bug since this one was for the first
leak. Also please attach the full valgrind output. Thx!

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