Summary: | Mail snapshot has black webview in multitasking switcher | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Tim Horton <thorton> | ||||
Component: | New Bugs | Assignee: | Tim Horton <thorton> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | andersca, barraclough, cdumez, simon.fraser | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Tim Horton
2016-06-22 13:10:00 PDT
Created attachment 281866 [details]
Patch
Comment on attachment 281866 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=281866&action=review > Source/WebKit2/ChangeLog:18 > + UIKit suggested instead waiting for the window context teardown notification, > + which does indeed seem to fire after the snapshotting is complete. I have a small > + change to WebCore::IOSurface and RemoteLayerBackingStore that makes the problem > + much more reproducible, and this fixes it perfectly, while the layers still > + eventually end up being made volatile. A bit too much story-telling here. > Source/WebKit2/UIProcess/ApplicationStateTracker.mm:76 > -ApplicationStateTracker::ApplicationStateTracker(UIView *view, SEL didEnterBackgroundSelector, SEL willEnterForegroundSelector) > +ApplicationStateTracker::ApplicationStateTracker(UIView *view, SEL didEnterBackgroundSelector, SEL didFinishSnapshottingAfterEnteringBackgroundSelector, SEL willEnterForegroundSelector) Why all this selector magic, rather than just an Obj-C protocol or something? |