Dear community and @eskimo
I am supporting and developing EPUB reader application which uses UIWebView for rendering EPUBs. All went smooth untill we decided to move to the WKWebview due to UIWebView depreciation in iOS12.
Our assumption is that OOM issue occurs on the old devices like iPad 2 when app is calculating content with help of WKWebView. While device is connected to a MacBook nothing appears in a debugger, connection just drops and app is terminated.
No crash reports are present. Just a line in a console log :
default 14:43:59.000000 +020204 com.apple.xpc.launchd Service exited due to signal: Killed: 9
The flow looks like this:
App loads UIPageview which launches 3 ViewControllers with WKWebview.
One for current page, another one for previous and one for next.
Three WKWebViews in total.
- The same time another NSOperation starts and app goes through each html chapter making invisible rendering to calculate pages.
For some books app just terminates about 70% of progress without any info in debugger. Small books works fine.
Due to the nature of WKWebview i can’t see anything connected to it in allocation instrument.
Would you be so kind to recommend best practice how i should debug this? And some ideas about solutions?