<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#c13">Comment # 13</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:darin@apple.com" title="Darin Adler <darin@apple.com>"> <span class="fn">Darin Adler</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147036#c12">comment #12</a>)
<span class="quote">> So, would you be opposed to leave the exit(0) for other ports and quit the
> main loop for GTK+ only?</span >
Yes, I am opposed to it. Not necessarily strongly opposed, but I don’t want to do this in WebKit.
<span class="quote">> Otherwise I will just remove the platformFinalize
> and use a compiler destructor instead.</span >
In case it’s not clear, I’m opposed to that too.
WebKit should not have code that relies on running when the process exits. Not good architecture.</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>