[Webkit-unassigned] [Bug 186653] Add release assertion against destroying WebProcessPool from networkProcessFailedToLaunch callback

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jun 15 09:02:08 PDT 2018


--- Comment #11 from Brady Eidson <beidson at apple.com> ---
(In reply to Antti Koivisto from comment #10)
> > Why don't we protect |this| in networkProcessFailedToLaunch() ?
> That's not going to be sufficient. The protection needs to be lower on the
> stack and other things (NetworkProcessProxy) will need to be protected too.

In the storage process case that is absolutely not true.

Please try to reproduce this with an API test now that I've described the behavior of how these process pools can come into existence and then be destroyed.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20180615/c1a1ea39/attachment.html>

More information about the webkit-unassigned mailing list