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.

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

Segmentation fault on bun:test (with watch infinite loop) #11469

Closed
coratgerl opened this issue May 30, 2024 · 1 comment
Closed

Segmentation fault on bun:test (with watch infinite loop) #11469

coratgerl opened this issue May 30, 2024 · 1 comment
Labels
crash An issue that could cause a crash

Comments

@coratgerl
Copy link
Contributor

How can we reproduce the crash?

const fn = async () => {}

it('should', async () => {
  expect(fn()).resolves.not.toThrow('anything here')
})

JavaScript/TypeScript code that reproduces the crash?

No response

Relevant log output

No response

Stack Trace (bun.report)

Bun v1.1.10 (5102a94) on macos aarch64 [TestCommand]

Segmentation fault at address 0x00000005

  • 2 unknown/js code
  • src.install.semver.SemverObject.order
  • ExpectPrototype__toThrow
  • WebCore::ExpectPrototype__toThrowCallback
  • 1 unknown/js code
  • llint_entry
  • 1 unknown/js code
  • llint_entry
  • vmEntryToJavaScript
@coratgerl coratgerl added the crash An issue that could cause a crash label May 30, 2024
@dylan-conway
Copy link
Collaborator

This is fixed in bun v1.1.24, most likely with #13272

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crash An issue that could cause a crash
Projects
None yet
Development

No branches or pull requests

2 participants