Summary: | [iOS] A WebPageProxy in closed state should not be allowed to hold a process assertion | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Chris Dumez <cdumez> | ||||
Component: | WebKit2 | Assignee: | Chris Dumez <cdumez> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | andersca, barraclough, dbates, kling, rniwa, sam, thorton, webkit-bug-importer | ||||
Priority: | P1 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | iOS 9.3 | ||||||
Attachments: |
|
Description
Chris Dumez
2016-06-23 12:22:49 PDT
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. |