You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that there is some limit we hit on Safari related to call stack size. Loading a greenfield Rails application (Rails.application.initialize!, eager_load is true) results in a maximum call stack size exceeded error. The crash dump only shows ~100 stack frames.
I got some reports that this issue is reproducible on https://ruby-quiz-2025.storesinc.tech at Kaigi... 😢
I had a second look at this but it seems like our iseq_compile_each0 and pm_compile_node are consuming too wasm stack on WebKit.
It seems that there is some limit we hit on Safari related to call stack size. Loading a greenfield Rails application (
Rails.application.initialize!
, eager_load is true) results in a maximum call stack size exceeded error. The crash dump only shows ~100 stack frames.dump.txt
What's interesting is that simply calling a recursive method hits the stack level too deep error at much higher values, see, for example: https://runruby.dev/?gist=84cc1d932b19755f45d9ec52b20567f2
Details
Ruby Version: 3.3.0.
rbwasm version: 2.6.2
js version: 2.6.2
The RubyVM information is as follows:
Other
Some possibly related issues found in the wild:
The text was updated successfully, but these errors were encountered: