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
is hit, looking like a stack overflow or so is the underlying cause. The surrounding stack trace indicates that there is a longer sequence of PrecomputingExpressionRunner::visits, further substantiating the assumption:
And indeed, when increasing stack size to -sSTACK_SIZE=655360, the errors go away in both debug and release builds, so my guess is that the default stack size of 65536 is a little low.
The text was updated successfully, but these errors were encountered:
CountBleck
added a commit
to CountBleck/binaryen.js
that referenced
this issue
Apr 9, 2023
That seems likely, yes. Emscripten lowered the default stack size to 64K recently, which is usually enough, but Binaryen does do some deep recursions. Avoiding recursion might be useful in the long term, but for now we should increase the default stack size in Binaryen. The old 5MB is probably fine as binaryen.js doesn't need to run in highly-constrained memory environments AFAIK.
Recently, a bunch of strange issues have appeared in conjunction with Binaryen.js builds, yielding runtime errors like
RuntimeError: null function or function signature mismatch
andTypeError: c(...) is not a function
as described in more detail in AssemblyScript/assemblyscript#2682 and AssemblyScript/assemblyscript#2683.
After getting debug builds to work again as outlined in #5647, it turned out that the
__assert_fail
inis hit, looking like a stack overflow or so is the underlying cause. The surrounding stack trace indicates that there is a longer sequence of
PrecomputingExpressionRunner::visit
s, further substantiating the assumption:And indeed, when increasing stack size to
-sSTACK_SIZE=655360
, the errors go away in both debug and release builds, so my guess is that the default stack size of65536
is a little low.The text was updated successfully, but these errors were encountered: