Segmentation fault during `bun --filter '*' dev`

[eknowles]

How can we reproduce the crash?

• Running in devcontainer.
• Have two workspaces (app/server)

bun i works as does the same thing...

Bun.spawn(["bun", "run", "dev"], {
  cwd: "./apps/client",
});

Bun.spawn(["bun", "run", "dev"], {
  cwd: "./apps/server",
});

Relevant log output

vscode ➜ /workspace (main) $ bun --filter '*' dev
============================================================
Bun v1.1.36 (ededc168) Linux arm64
Linux Kernel v6.10.4 | glibc v2.31
Args: "bun" "--filter" "*" "dev"
Elapsed: 11ms | User: 0ms | Sys: 4ms
RSS: 1.07GB | Peak: 11.51MB | Commit: 1.07GB | Faults: 0

panic(main thread): Segmentation fault at address 0x6024C
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

To send a redacted crash report to Bun's team,
please file a GitHub issue using the link below:

 https://bun.report/1.1.36/La1ededc16AA+5Dm65x2Cm/og8C2z7p5C2kmn0C2n2l0Cu9mImz0l0CA2A4khY

[1]    13691 trace trap  bun --filter '*' dev

Stack Trace (bun.report)

Bun v1.1.36 (ededc16) on linux aarch64 [AutoCommand]

Segmentation fault at address 0x0006024C

• alloc.rs:0: ??
• semver.zig:582: src.install.dependency.parseWithTag
• dependency.zig:851: src.resolver.package_json.PackageJSON.parse__anon_106905
• filter_run.zig:475: src.cli.filter_run.runScriptsWithFilter
• cli.zig:2076: src.cli.Cli.start
• main.zig:48: main
• ??
• _start

_{Sentry Issue: BUN-8S9}

[Jarred-Sumner]

Fixed in Bun v1.1.37. try running bun upgrade --canary or wait till tomorrow for the release

This was a regression in v1.1.35