I recently noticed a very large drop in reported/profiled memory consumption for an app when migrating from UIWebView to WKWebView.
I suspect that the memory being consumed by WKWebView is not showing up as memory used by the app and is therefore perhaps running in another process?
Does anyone know if memory consumed by WKWebView is considered by the OS as used by the app, and therefore contributes to the figure which might give rise to a memory warning or cause the app to be evicted from memory in the background?
This would be a significant advantage over UIWebView if so and a good motivator to press through the other specific problems I am experiencing with WKWebView and the migration.
Hi tenermobile
Yes, WKWebView performs all of its work out of process and its memory usage is accounted for seperately from that of your app. While its possible that the WKWebView process could exceed its memory budget, doing so would not cause your app to be terminated and should at most result in a blank view.