[Webkit-unassigned] [Bug 233436] [GTK] Running webkit programs are unstable after version upgrades

[bugzilla-daemon at webkit.org]

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

Adrian Perez <aperez at igalia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aperez at igalia.com

--- Comment #3 from Adrian Perez <aperez at igalia.com> ---
(In reply to Michael Catanzaro from comment #2)
> We could emit a signal on WebKitWebContext. The application would then have
> the opportunity to display UI suggesting that the user restart.
> 
> > Detecting the version mismatch and respawning the affected process may mitigate the problem but it probably won't cover all cases and it's maybe not worth the added complexity.
> 
> Patrick's right: you'd have to restart the UI process as well, which is
> impossible, not just the child processes. Another impossible alternative
> would be to never start new child processes. I would expect WebKit to
> continue working fine so long as no new processes are started.

Exactly. This is why Firefox and Chrom{e,ium} will offer you to restart
the whole browser after an upgrade.

> Here's something that might actually work: we could copy the subprocess
> binaries into a private location under /run when the UI process starts,
> before launching anything. If each UI process had its own separate copies of
> its subprocess binaries, as they existed at the time the UI process was
> launched, then WebKit would be robust to system upgrades. I don't think
> that's worth the effort, but it *should* work.

I'd say it's not worth it.

-- 
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/20211123/19bc6745/attachment-0001.htm>