<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#c18">Comment # 18</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:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=152043#c17">comment #17</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=152043#c6">comment #6</a>)
> > I still think it's the caller that is creating a WebKitWebSourceGStreamer in
> > a secondary thread the one to be fixed.
>
> 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.</span >
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.</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>