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 looks like most of the time is spent in the allocU8Array call here, but the exception (a simple number, like 2153016872) is thrown in the binaryen._BinaryenSetMemory call without any delay there. I'll look into it a bit more.
Activity
CountBleck commentedon Mar 24, 2024
It looks like most of the time is spent in the
allocU8Array
call here, but the exception (a simple number, like 2153016872) is thrown in thebinaryen._BinaryenSetMemory
call without any delay there. I'll look into it a bit more.CountBleck commentedon Mar 24, 2024
Hm, I can only guess that it has something to do with the copy here, since binaryen.js's memory might hit the 4 GiB limit there.
Do not allocate MemorySegments for memory.data(i32, i32?)
Do not allocate buffers for memory.data(i32, i32?)
fix: Do not allocate buffers for memory.data(i32, i32?)
BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)
BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)
BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)