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

Crash when requiring native addon on Windows #13566

Open
osztenkurden opened this issue Aug 27, 2024 · 0 comments
Open

Crash when requiring native addon on Windows #13566

osztenkurden opened this issue Aug 27, 2024 · 0 comments
Labels
crash An issue that could cause a crash napi Compatibility with the native layer of Node.js runtime windows An issue that is known to occur on Windows

Comments

@osztenkurden
Copy link

How can we reproduce the crash?

https://replit.com/@hubertwalczak8/Bun-Crash-with-Native-Addon-on-Windows#index.ts

Basically, I'm doing native addon in zig for data parser, and bun crashes out whenever I require the addon on Windows. Not sure if this is the same as #4290

Relevant log output

No output beside this:

F:\Repositories\playground>bun testworker.ts
============================================================
Bun v1.1.26 (0a37423b) Windows x64
Windows v.win10_fe
CPU: sse42 avx avx2
Args: "bun" "testworker.ts"
Features: jsc tsconfig 
Builtins: "bun:main" 
Elapsed: 41ms | User: 15ms | Sys: 31ms
RSS: 98.36MB | Peak: 98.37MB | Commit: 0.15GB | Faults: 24229

panic(main thread): Segmentation fault at address 0xFFFFFFFFFFFFFFFF
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:

Stack Trace (bun.report)

Bun v1.1.26 (0a37423) on windows x86_64 [AutoCommand]

Segmentation fault at address 0xFFFFFFFFFFFFFFFF

  • ??? at 0x2d0931 in node.exe
  • ??? at 0x1056 in example.node
  • BunProcess.cpp:411: Bun::Process_functionDlopen
  • 2 unknown/js code
  • llint_entry
@osztenkurden osztenkurden added the crash An issue that could cause a crash label Aug 27, 2024
@github-actions github-actions bot added runtime windows An issue that is known to occur on Windows crash reporter bug the stack trace given does not seem to be valid napi Compatibility with the native layer of Node.js labels Aug 27, 2024
@Jarred-Sumner Jarred-Sumner removed the crash reporter bug the stack trace given does not seem to be valid label Aug 27, 2024
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 napi Compatibility with the native layer of Node.js runtime windows An issue that is known to occur on Windows
Projects
None yet
Development

No branches or pull requests

2 participants