[Bug 776540] GstGL: Occasional assertion failures on GST_IS_GL_DISPLAY and GST_IS_GL_CONTEXT

[GStreamer (GNOME Bugzilla)]

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

--- Comment #23 from Petros <petroskataras at gmail.com> ---
I had a run with :

G_SLICE=always-malloc
G_DEBUG=gc-friendly

valgrind ./Application

and the only thing it reports is the following during runtime :

Pipeline state changed from : NULL to READY with pending VOID_PENDING
==9989== Thread 23 gstglcontext:
==9989== Conditional jump or move depends on uninitialised value(s)
==9989==    at 0x10DDFFBF: ??? (in
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.367.35)
==9989==    by 0x10DE0DE8: ??? (in
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.367.35)
==9989==    by 0x1092AF46: ??? (in
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.367.35)
==9989==    by 0x70AED34: gst_gl_query_end (gstglquery.c:282)
==9989==    by 0x7090DF5: gst_gl_memory_texsubimage (gstglmemory.c:541)
==9989==    by 0x7093727: _upload_pbo_memory (gstglmemorypbo.c:151)
==9989==    by 0x7093727: _gl_mem_map_gpu_access (gstglmemorypbo.c:338)
==9989==    by 0x7093727: _gl_mem_map (gstglmemorypbo.c:362)
==9989==    by 0x708E135: _map_data_gl (gstglbasememory.c:261)
==9989==    by 0x708BE17: gst_gl_context_thread_add (gstglcontext.c:1537)
==9989==    by 0x708DD7D: _mem_map_full (gstglbasememory.c:295)
==9989==    by 0x66B64DF: gst_memory_map (gstmemory.c:303)
==9989==    by 0x709E400: _do_convert_one_view (gstglcolorconvert.c:2174)
==9989==    by 0x70A0749: _do_convert (gstglcolorconvert.c:2422)
==9989== 
Pipeline state changed from : READY to PAUSED with pending VOID_PENDING
Playing: 0
Pipeline state about to change from : NULL to READY
Pipeline state changed SUCCESSFULLY from : NULL to READY
Pipeline state changed from : NULL to READY with pending VOID_PENDING
Need context gst.gl.GLDisplay from element convert
Need context gst.gl.app_context from element convert
Pipeline state about to change from : READY to PAUSED
Pipeline state change will happen ASYNC from : READY to PAUSED
==9989== Conditional jump or move depends on uninitialised value(s)
==9989==    at 0x10DDFFBF: ??? (in
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.367.35)
==9989==    by 0x10DE0DE8: ??? (in
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.367.35)
==9989==    by 0x7090D85: gst_gl_memory_texsubimage (gstglmemory.c:537)
==9989==    by 0x7093727: _upload_pbo_memory (gstglmemorypbo.c:151)
==9989==    by 0x7093727: _gl_mem_map_gpu_access (gstglmemorypbo.c:338)
==9989==    by 0x7093727: _gl_mem_map (gstglmemorypbo.c:362)
==9989==    by 0x708E135: _map_data_gl (gstglbasememory.c:261)
==9989==    by 0x708BE17: gst_gl_context_thread_add (gstglcontext.c:1537)
==9989==    by 0x708DD7D: _mem_map_full (gstglbasememory.c:295)
==9989==    by 0x66B64DF: gst_memory_map (gstmemory.c:303)
==9989==    by 0x709E400: _do_convert_one_view (gstglcolorconvert.c:2174)
==9989==    by 0x70A0749: _do_convert (gstglcolorconvert.c:2422)
==9989==    by 0x70A3D22: _run_message_sync (gstglwindow.c:617)
==9989==    by 0x70A3CC1: _run_message_async (gstglwindow.c:684)
==9989==

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