Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bun install crash with lockfile on Bun v1.0.3 #5569

Closed
Electroid opened this issue Sep 16, 2023 · 4 comments
Closed

bun install crash with lockfile on Bun v1.0.3 #5569

Electroid opened this issue Sep 16, 2023 · 4 comments
Labels
bug Something isn't working crash An issue that could cause a crash npm Something that relates to the npm-compatible client

Comments

@Electroid
Copy link
Contributor

Electroid commented Sep 16, 2023 •
edited

On macOS arm:

❯ bun install bufferutil
bun add v1.0.3 (b651b16f)
fish: Job 1, 'bun install bufferutil' terminated by signal SIGSEGV (Address boundary error)

Attached lockfile:
bun.lockb.zip

Problem goes away when lockfile is removed and regenerated.
@Electroid Electroid added bug Something isn't working crash An issue that could cause a crash npm Something that relates to the npm-compatible client labels Sep 16, 2023
@Electroid Electroid changed the title bun install crash with bufferutil bun install crash with lockfile Sep 16, 2023
@IndigoCurnick
Copy link

Similar issue here - except it hangs forever. Deleting bun.lockb and running bun install works. This issue happens to me when I pull repos which have the bun.lockb from GitHub, from someone else's machine.

@Jarred-Sumner
Copy link
Collaborator

Are you on bun v1.0.32 ?

@IndigoCurnick
Copy link

I'm on bun v1.0.33, ArchLinux

@Jarred-Sumner Jarred-Sumner changed the title bun install crash with lockfile bun install crash with lockfile on Bun v1.0.3 Aug 29, 2024
@Jarred-Sumner
Copy link
Collaborator

If anyone runs into this issue in the future, please include the package.json and bun.lockb in the issue.

This crash was very likely fixed, but at this point it's not actionable without a way to reproduce it.

@Jarred-Sumner Jarred-Sumner closed this as not planned Won't fix, can't repro, duplicate, stale Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working crash An issue that could cause a crash npm Something that relates to the npm-compatible client
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Jarred-Sumner @Electroid @IndigoCurnick