<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SOUP] Network process crash in WebKit::CustomProtocolManagerImpl::didFailWithError"
href="https://bugs.webkit.org/show_bug.cgi?id=165082#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SOUP] Network process crash in WebKit::CustomProtocolManagerImpl::didFailWithError"
href="https://bugs.webkit.org/show_bug.cgi?id=165082">bug 165082</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=165082#c14">comment #14</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=165082#c12">comment #12</a>)
> > ...and setCustomProtocolManager to call the
> > std::unique_ptr constructor explicitly.
> Woah, definitely don't do this. Use unique_ptr properly if we make this
> change.
>
> Why not just make the soup custom protocol handler thread safe? I think it
> would be strange to have one port be a work queue message receiver and one
> port not.</span >
Because we don't want jumps from one thread to the other and mutexes if we can just use the main 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>