[Webkit-unassigned] [Bug 201028] [WebAssembly] iOS 13 RangeError: Maximum call stack size exceeded.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Oct 31 17:06:52 PDT 2019


--- Comment #8 from Katelyn Gadd <kg at luminance.org> ---
The massive drop in iOS 13 explains a lot - I wasn't able to test that and don't have an iOS 12 device to compare. We were observing regressions in desktop Safari as well, which I couldn't reproduce.

The Sleep solution is only going to work for very very large modules (ours are in the dozens of MB) and the fact that the required delay changes between devices suggests that it's based on compile speeds or something.

Interesting to see a stack depth limit of 15k for you. I approached around 80k in Safari on Catalina w/a recursive function that accepts 4 int32 arguments. Chrome and Firefox don't go as far, and their limits are dramatically different between Catalina and Windows 10. I suspect there's variability here based on other factors.

Being able to dump the generated JITcode for our functions would help us identify what's going on, but I haven't been able to find a way to do this other than doing some really complex trickery in a debugger - only possible on PC, not iOS - or compiling JSC from source, which would require us to know the exact build configuration Safari uses.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191101/f9d47641/attachment.htm>

More information about the webkit-unassigned mailing list