In previous versions of iOS (9 and 10), we have been able to reload the webview when it web content process is terminated by WebKit. Unfortunately, this behaves much differently when running on an iOS 11 device. Trying the same thing to recover on iOS 11, results in a partial web page rendering. When reloading in this scenario, only the portion of the web view within it's parent view bounds is rendered. If you try scrolling down the page, you'll notice that anything below the top portion of the web page is not rendered at all. Then try navigating to a different URL or even loading a new request, yet the same result occurs. It seems that WebKit is trying to optimize too much. The only way I can fix this, is to destroy the WKWebView by setting it to nil and creating it once again, then loading a request with the previous URL that was cached. This webview destruction is a workaround. It is far form ideal. I assume this either a bug or a change in iOS 11 WebKit that needs attention, since it does not affect 9 or 10. Please advise on the status of this bug.
Please attach a test application that shows this bug.
<rdar://problem/34415016>
Created attachment 320896 [details] Demonstrates bug with web content process termination and web page rendering. Please check out the README in the project.
Any headway with this? I can provide more detail if needed.
I am unable to run the test app on iOS 11: dyld: Library not loaded: /System/Library/PrivateFrameworks/Swift/libswiftSwiftOnoneSupport.dylib Referenced from: /Applications/WKWebViewBugSample.app/WKWebViewBugSample Reason: image not found
(In reply to Chris Dumez from comment #5) > I am unable to run the test app on iOS 11: > dyld: Library not loaded: > /System/Library/PrivateFrameworks/Swift/libswiftSwiftOnoneSupport.dylib > Referenced from: /Applications/WKWebViewBugSample.app/WKWebViewBugSample > Reason: image not found Nevermind, worked around it.
I can now run the test app on iOS 11. If I open many tabs and switch quickly through them, I do see that some of them are getting jetsam'd and that they are white for a second before reloading. However, once reloaded, I can scroll through the tab just fine. So far, I have not been able to reproduce the issue that was reported.
(In reply to Chris Dumez from comment #7) > I can now run the test app on iOS 11. If I open many tabs and switch quickly > through them, I do see that some of them are getting jetsam'd and that they > are white for a second before reloading. However, once reloaded, I can > scroll through the tab just fine. > > So far, I have not been able to reproduce the issue that was reported. It is not 100% reproducible but I was able to reproduce it.
*** This bug has been marked as a duplicate of bug 178095 ***
Should be fixed now, thanks for the test app.
No problem. Thank you!
When will this revision of webKit be dropped into public iOS?
(In reply to Logan Blevins from comment #12) > When will this revision of webKit be dropped into public iOS? We are not allowed to make comments about unreleased products.