<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GStreamer] MainThreadNotifier ASSERTION FAILED: m_boundThread == currentThread() in _WebKitWebSrcPrivate::~_WebKitWebSrcPrivate"
href="https://bugs.webkit.org/show_bug.cgi?id=152043#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GStreamer] MainThreadNotifier ASSERTION FAILED: m_boundThread == currentThread() in _WebKitWebSrcPrivate::~_WebKitWebSrcPrivate"
href="https://bugs.webkit.org/show_bug.cgi?id=152043">bug 152043</a>
from <span class="vcard"><a class="email" href="mailto:calvaris@igalia.com" title="Xabier RodrÃguez Calvar <calvaris@igalia.com>"> <span class="fn">Xabier RodrÃguez Calvar</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=152043#c18">comment #18</a>)
<span class="quote">> > The creation of WebKitWebSourceGStreamer isn't under the control of the
> > application. That GstElement is created automatically by GStreamer during
> > the pipeline negotiation, and that can happen on a streaming (ie: non-main)
> > thread depending on the pipeline topology.
>
> And we detect it now, so It's still the caller that creates the object in a
> secondary the thread the one who should delete it in the same thread.</span >
We are facing here two requirements colluding. First is that GStreamer has the right to create and destroy objects in the threads they see fit, which is what is happening. Second is the requirement of WeakPtrFactory of begin created and destroyed from the same thread.
We'll think about the proper fix.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>