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 at address 0xFFFE000000000012 #16467

Open
ElYaiko opened this issue Jan 17, 2025 · 2 comments
Open

Segmentation fault at address 0xFFFE000000000012 #16467

ElYaiko opened this issue Jan 17, 2025 · 2 comments
Labels
crash An issue that could cause a crash linux An issue that occurs on Linux needs repro Needs an example to reproduce

Comments

@ElYaiko
Copy link

ElYaiko commented Jan 17, 2025

How can we reproduce the crash?

I'm running puppeeter with Bun and crashes randomly. (Didn't happen before)

Relevant log output

Stack Trace (bun.report)

Bun v1.1.44-canary (9579e42) on linux aarch64 [AutoCommand]

Segmentation fault at address 0xFFFE000000000012

Features: process_dlopen, Bun.stderr, Bun.stdin, Bun.stdout, WebSocket, dotenv, fetch, jsc, shell, spawn, transpiler_cache, tsconfig, tsconfig

Sentry Issue: BUN-5Z

@ElYaiko ElYaiko added the crash An issue that could cause a crash label Jan 17, 2025
@github-actions github-actions bot added the linux An issue that occurs on Linux label Jan 17, 2025
@190n 190n added the needs repro Needs an example to reproduce label Jan 17, 2025
Copy link
Contributor

Hello @ElYaiko. Please provide a minimal reproduction using a GitHub repository, Replit, CodeSandbox, or provide a bulleted list of commands to run that reproduce this issue. Issues marked with needs repro will be closed if they have no activity within 3 days.

@190n
Copy link
Contributor

190n commented Jan 17, 2025

Interested to see a reproduction if you can share one. The fault address looks like the JSValue representation of 0x12 as an integer:

     *     Pointer {  0000:PPPP:PPPP:PPPP
     *              / 0002:****:****:****
     *     Double  {         ...
     *              \ FFFC:****:****:****
     *     Integer {  FFFE:0000:IIII:IIII

But we shouldn't ever dereference such a value since it's tagged as an integer, not a pointer. Maybe this is a race condition where one thread tries to read a value thinking it's a pointer while another thread simultaneously replaces the value with an integer?

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 linux An issue that occurs on Linux needs repro Needs an example to reproduce
Projects
None yet
Development

No branches or pull requests

2 participants