Bug 110015 – [GStreamer] GstBus leak

• Status: RESOLVED
• Resolution: DUPLICATE
• Component: WebKitGTK

[Priit Laes (IRC: plaes)]

This is with webkit-gtk-1.11.5 and Quake from http://www.quaddicted.com/stuff/WebQuake/Client/WebQuake.htm

(epiphany:25272): GStreamer-CRITICAL **: gst_poll_get_read_gpollfd: assertion `set != NULL' failed

(epiphany:25272): GStreamer-CRITICAL **: gst_poll_write_control: assertion `set != NULL' failed

(epiphany:25272): GStreamer-CRITICAL **: gstsystemclock: write control failed in wakeup_async: 24:Too many open files


(epiphany:25272): GStreamer-CRITICAL **: gst_poll_free: assertion `set != NULL' failed
[New Thread 0x7ffded15b700 (LWP 25993)]
[New Thread 0x7ffdec95a700 (LWP 25994)]

(epiphany:25272): GStreamer-CRITICAL **: gst_poll_get_read_gpollfd: assertion `set != NULL' failed

(epiphany:25272): GStreamer-CRITICAL **: gst_bus_create_watch: assertion `bus->priv->poll != NULL' failed

(epiphany:25272): GLib-CRITICAL **: g_source_set_callback: assertion `source != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
g_source_attach (source=0x0, context=0x0) at gmain.c:1077
1077	gmain.c: No such file or directory.
(gdb) bt
#0  g_source_attach (source=0x0, context=0x0) at gmain.c:1077
#1  0x00007fffeec4b9fa in gst_bus_add_watch_full_unlocked (notify=<optimized out>, user_data=0x0, 
    func=0x7fffeec4a750 <gst_bus_async_signal_func>, priority=<optimized out>, bus=<optimized out>) at gstbus.c:867
#2  gst_bus_add_watch_full_unlocked (bus=<optimized out>, priority=<optimized out>, 
    func=0x7fffeec4a750 <gst_bus_async_signal_func>, user_data=0x0, notify=<optimized out>) at gstbus.c:846
#3  0x00007fffeec4bd3e in gst_bus_add_signal_watch_full (bus=0x7fff64a3ea30, priority=0) at gstbus.c:1256
#4  0x00007ffff6514aca in WebCore::MediaPlayerPrivateGStreamer::createGSTPlayBin () from /usr/lib64/libwebkitgtk-3.0.so.0
#5  0x00007ffff65156f8 in load () from /usr/lib64/libwebkitgtk-3.0.so.0
#6  0x00007ffff62ed875 in WebCore::MediaPlayer::loadWithNextMediaEngine () from /usr/lib64/libwebkitgtk-3.0.so.0
#7  0x00007ffff62edc84 in WebCore::MediaPlayer::load () from /usr/lib64/libwebkitgtk-3.0.so.0
#8  0x00007ffff59be277 in WebCore::HTMLMediaElement::loadResource () from /usr/lib64/libwebkitgtk-3.0.so.0
#9  0x00007ffff59be6e2 in WebCore::HTMLMediaElement::selectMediaResource () from /usr/lib64/libwebkitgtk-3.0.so.0
#10 0x00007ffff59be938 in WebCore::HTMLMediaElement::loadTimerFired () from /usr/lib64/libwebkitgtk-3.0.so.0
#11 0x00007ffff6398fba in WebCore::ThreadTimers::sharedTimerFiredInternal () from /usr/lib64/libwebkitgtk-3.0.so.0
#12 0x00007ffff653a6e2 in timeout_cb () from /usr/lib64/libwebkitgtk-3.0.so.0
#13 0x00007ffff1a6e3db in g_timeout_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>)
    at gmain.c:4026
#14 0x00007ffff1a6d813 in g_main_dispatch (context=0x70dec0) at gmain.c:2715
#15 g_main_context_dispatch (context=0x70dec0) at gmain.c:3219
#16 0x00007ffff1a6db60 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x70dec0, self=<optimized out>)
    at gmain.c:3290
#17 g_main_context_iterate (context=0x70dec0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3227
#18 0x00007ffff1a6dc24 in g_main_context_iteration (context=0x70dec0, may_block=1) at gmain.c:3351
#19 0x00007ffff2894204 in g_application_run (application=0x871000, argc=<optimized out>, argv=0x7fffffffd868)
    at gapplication.c:1624
#20 0x0000000000433c30 in main (argc=1, argv=0x7fffffffd868) at ephy-main.c:499
(gdb)

[Philippe Normand]

I assume this is with GStreamer 1.0 ?

[Priit Laes (IRC: plaes)]

(In reply to comment #1)
> I assume this is with GStreamer 1.0 ?

Yes, gstreamer-1.0: v1.0.5

[Philippe Normand]

The game seems up again, I basically get the same behavior as in bug 32281. Too many threads :(

That game loads a bunch of audio elements with data: uris... Seems to me WebAudio would be a better approach for this.

[Chris Dumez]

I wonder if this is a duplicate of Bug 107544. The backtrace seems to be the same at least.

[Philippe Normand]

*** This bug has been marked as a duplicate of bug 107544 ***