A WebPageProxy in closed state should not be allowed to hold a process assertion. It currently happens that WebPageProxy::close() gets called but that the WebPageProxy is kept alive by Safari (e.g. In case of top-hit preloading). In such cases, we fail to release the foreground process assertion that the WebPageProxy holds. We should clear the foreground process assertion that the WebPageProxy holds as soon as WebPageProxy::close() is called.
rdar://problem/17665473
Created attachment 281928 [details] Patch
Comment on attachment 281928 [details] Patch It doesn't make sense for Safari to keep the view alive if it has been closed; you can't come back from being closed, as far as I remember. Are you sure that is intentional?
(In reply to comment #3) > Comment on attachment 281928 [details] > Patch > > It doesn't make sense for Safari to keep the view alive if it has been > closed; you can't come back from being closed, as far as I remember. Are you > sure that is intentional? It may not be intentional, I'll investigate separately. I definitely see close() getting called but not the destructor. Do you mind if we still land as is though? It cannot hurt to release the assertion as soon as close() is called I believe.
Comment on attachment 281928 [details] Patch Clearing flags on attachment: 281928 Committed r202393: <http://trac.webkit.org/changeset/202393>
All reviewed patches have been landed. Closing bug.