<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] WebProcessMain::platformFinalize() is not called when web process finished with exit(0)"
href="https://bugs.webkit.org/show_bug.cgi?id=147036#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] WebProcessMain::platformFinalize() is not called when web process finished with exit(0)"
href="https://bugs.webkit.org/show_bug.cgi?id=147036">bug 147036</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=147036#c8">comment #8</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=147036#c4">comment #4</a>)
> > For GTK it is the code Carlos is adding to save the clipboard contents in
> > the clipboard manager, so that you can paste data that you copied from a web
> > process after closing the web process.
>
> It would be much better to do that earlier, perhaps based on some coalescing
> timer. You don’t want to lose the clipboard if the web process crashes.
> Generally it’s not a good pattern to have any code that runs only on exit.
> One of the main benefits of having a web process is better behavior if a
> crash occurs.</span >
gtk_clipboard_store() is expected to be called only when the application is about to quit, and that's what all GTK+ applications do, because GTK calls it after the main loop quits. We could use a compiler destructor to do all the cleanup though, but I still thing exit(0) is not the best way to finish the web process when we can just quit the main loop, and finish properly from main.</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>