Crash when using `bun test [query]` and most of the time `bun run`

[n0thhhing]

What version of Bun is running?

Tested on bun 1.1.1, 1.0, and 1.0.32

What platform is your computer?

• Linux 6.2.1-PRoot-Distro aarch64 Debian GNU/Linux 12 (bookworm), Arch Linux, and Ubuntu 23.10

What is the expected behavior?

bun test disasm iter
bun test v1.0.32 (5fec71bd)

src/tests/disasm.test.ts:
✓ disasm ARM64 [116.60ms]

src/tests/iter.test.ts:
✓ disasm_iter ARM [44.74ms]
✓ disasm_iter ARM64 [10.77ms]

What do you see instead?

On Arch Linux and Debian, this issue occurs frequently, while on Ubuntu, it consistently happens.

╰─ bun test disasm it
- bun test v1.0.32 (5fec71bd)

src/tests/disasm.test.ts:
fish: Job 1, 'bun test disasm it' terminated by signal SIGSEGV (Address boundary error)

For bun run:

bun run src/tests/disasm.test.ts
fish: Job 1, 'bun run src/tests/disasm.test.ts' terminated by signal SIGSEGV (Address boundary error)

What steps can reproduce the bug?

No additional build steps are required to run the code, as all necessary files have already been generated using Emscripten. You can find the code to reproduce the issue on the SIGSEGV branch of the capstone-wrapper repository.

- Running `bun test disasm iter` results in immediate termination (SIGSEGV) without executing any code.
- Alternatively, `bun run src/tests/disasm*` should technically be
  executable but behaves similarly to 'bun test' by throwing a SIGSEGV
  error. This indicates that the issue may not be with the code itself,
  but rather with the parsing or transpiling process. Notably,
  even adding `console.log` statements at the top level does not
  produce any output in either case.

The primary source files, where most functions originate from, are src/wrapper.ts and src/memory.ts. While memory.ts doesn't technically execute any code, wrapper.ts serves as the entry point, initializing the Emscripten instance and importing a significant portion of the codebase. It's noteworthy that neither of these files throws any errors when executed.

Additional information

• The errors started occurring as the project grew in size, reaching around 200,000-300,000 lines of code.

• While aarch64 isn't directly supported with Termux, using proot resolves most platform-related issues.

• No code is executed AT ALL; it fails instantly even with top-level Emscripten stack tracing.

• Emscripten is used for transpilation, which can produce large files. However, running the code on Node.js works fine even with large files.

• Minifying the code will not resolve the issue.

• The project is being developed for aarch64 because it's meant to run on another project I'm working on

• The issue is not related to Emscripten because running src/wrapper.ts (where Emscripten is initialized) does not throw any errors.

  • Also note that using buns bundler on this code throws the following error, which is why I can't use node in the first place

    make bundle
    bun build/scripts/bundle.ts
    make: *** [Makefile:17: bundle] Segmentation fault

[n0thhhing]

This happends via bun run too also, it doesn't even throw the "Cannot use test() outside of the test runner. Run "bun test" to run tests" Error, it instantly throws segmentation fault(in most cases, sometimes it does work), also this will throw if the code is importing the wrapper.ts file

[KyrylR]

Have the same issue with bun test in CI: https://github.com/dl-solarity/zktype/actions/runs/8723755844/job/23932703629

Occurs not consistently but from time to time

[Jarred-Sumner]

Duplicate of #5398

[Jarred-Sumner]

This is a JavaScript transpiler stack overflow.

We will fix it, but to reduce the number of duplicated issues please follow along in #5398