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

Segmentation fault on "bun cdk diff" (regression, worked fine on 1.0.14) #7496

Closed
zenshixd opened this issue Dec 6, 2023 · 1 comment
Closed

Segmentation fault on "bun cdk diff" (regression, worked fine on 1.0.14) #7496

zenshixd opened this issue Dec 6, 2023 · 1 comment
Labels
bug Something isn't working crash An issue that could cause a crash

Comments

@zenshixd
Copy link
Contributor

zenshixd commented Dec 6, 2023

What version of Bun is running?

1.0.15

What platform is your computer?

Linux DESKTOP-LVO7EBH 5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

What steps can reproduce the bug?

  1. Clone https://github.com/zenshixd/mirrored-poe-trade
  2. bun i in root directory
  3. cd infra
  4. bun cdk diff

No need for aws credentials, it segfaults anyway.

What is the expected behavior?

cdk diff runs as expected

What do you see instead?

Segmentation fault, no cdk diff.

ubuntu@DESKTOP-LVO7EBH:~/Projects/mirrored-poe-trade/infra$ bun cdk diff
$ cdk diff
Segmentation fault

Subprocess exited with error 139
error: script "cdk" exited with code 1 (SIGHUP)

Additional information

It worked fine on 1.0.14.
@zenshixd zenshixd added the bug Something isn't working label Dec 6, 2023
@zenshixd zenshixd changed the title Segmentation fault on "bun cdk diff" Segmentation fault on "bun cdk diff" (regression, worked fine on 1.0.14) Dec 6, 2023
@paperclover paperclover added the crash An issue that could cause a crash label Dec 7, 2023
@paperclover
Copy link
Member

Duplicate of #5398

@paperclover paperclover marked this as a duplicate of #5398 Dec 7, 2023
@paperclover paperclover closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zenshixd @paperclover