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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=186653

--- Comment #9 from Brady Eidson <beidson at apple.com> ---
(In reply to Brady Eidson from comment #8)
> I'm working on a bug right now where it is known and *expected* that the
> WebProcessPool is getting destroyed, and therefore a protector is the right
> call.
> 
> Ping me for details or wait until I finish my API test which reproduces it :)

Actually mine is in StorageProcess related code, not NetworkProcess, but the general point still stands.

You can create a WKWebsiteDataStore that points to non-default locations on disk.
You can then use it for WebsiteData fetching or clearing.
You can do this without ever creating a process pool or a web view.
When you do so a process pool is created for you internally, and it's completely okay that said process pool is then destroyed.

You can look for my storage process example later today, or try to construct a network process example if you'd like (We *can* API test this)

-- 
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/45a31a18/attachment.html>