as crash when try to alloc large data #2827

Activity

1. HerrCai0907

   added

   bug

   on Mar 18, 2024
2. CountBleck

   self-assigned this

   on Mar 18, 2024
3. CountBleck commented on Mar 24, 2024

   

   CountBleck

   on Mar 24, 2024

   Member

   More actions

   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.
4. CountBleck commented on Mar 24, 2024

   

   CountBleck

   on Mar 24, 2024

   Member

   More actions

   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.
5. CountBleck

   added 2 commits that reference this issue on Mar 25, 2024

   Do not allocate MemorySegments for memory.data(i32, i32?)

   ...

   This issue will close once commit 373166c is merged into the 'main' branch.

   373166c

   Do not allocate buffers for memory.data(i32, i32?)

   ...

   This issue will close once commit 6a89a09 is merged into the 'main' branch.

   6a89a09
6. CountBleck

   added 4 commits that reference this issue on Apr 3, 2024

   fix: Do not allocate buffers for memory.data(i32, i32?)

   ...

   This issue will close once commit 559814d is merged into the 'main' branch.

   559814d

   BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

   ...

   This issue will close once commit ed50aef is merged into the 'main' branch.

   ed50aef

   BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

   ...

   This issue will close once commit 4465767 is merged into the 'main' branch.

   4465767

   BREAKING CHANGE: Do not allocate buffers for memory.data(i32, i32?)

   ...

   This issue will close once commit 163a631 is merged into the 'main' branch.

   163a631