NEW 221660
It is too easy to hit IPC throttling when calling -[WKWebView evaluateJavaScript:completionHandler:] 
https://bugs.webkit.org/show_bug.cgi?id=221660
Summary It is too easy to hit IPC throttling when calling -[WKWebView evaluateJavaScr...
Jonathan Deutsch
Reported 2021-02-09 23:27:08 PST
If you make too many JavaScript calls, you will hit: 2021-02-09 21:30:06.900010-0800 WebKitTester[66085:1768235] [IPC] 0x110c64160 - Connection::dispatchIncomingMessages: IPC throttling was triggered (has 13997 pending incoming messages, will only process 600 before yielding) 2021-02-09 21:30:06.903092-0800 WebKitTester[66085:1768235] [IPC] 0x110c64160 - Connection::dispatchIncomingMessages: first IPC message in queue is WebPageProxy_SetRenderTreeSize 2021-02-09 21:30:06.903403-0800 WebKitTester[66085:1768235] [IPC] 0x110c64160 - Connection::dispatchIncomingMessages: IPC throttling was triggered (has 13470 pending incoming messages, will only process 300 before yielding) 2021-02-09 21:30:06.903421-0800 WebKitTester[66085:1768235] [IPC] 0x110c64160 - Connection::dispatchIncomingMessages: first IPC message in queue is WebPage_RunJavaScriptInFrameInScriptWorldReply It isn't clear what the problem is, but I had to develop my own concatenation and deferred call system to deal with this. Apps like Tumult Hype [https://tumult.com/hype/] have deep integration between their data mode and web views. By limiting total calls, you make development less straight forward for apps like this.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-02-16 23:28:12 PST
<rdar://problem/74423384>
Note You need to log in before you can comment on or make changes to this bug.