WebAssembly / WebAssembly/binaryen
wasm-ctor-eval doesn't seem to play well with >2gb memories.
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
Looks like it runs out of memory maybe?
./test/runner core_2gb.test_eval_ctors_no_main --skip-slow --cores=4
...
em++: error: '/root/emsdk/upstream/bin/wasm-ctor-eval --ctors=_initialize --kept-exports=_initialize test_ctors_no_main.wasm -o test_ctors_no_main.wasm -g --mvp-features --enable-mutable-globals --enable-sign-ext' failed (received SIGKILL (-9))
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with ./test/runner core_2gb.test_eval_ctors_no_main --skip-slow --cores=4, then inspect the wasm-ctor-eval invocation shown in the error. Done means determining why memories over 2GB lead to SIGKILL and adding coverage that verifies the case no longer fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100