SonarSource / SonarSource/sonarqube-cli
Windows: sonar CLI commands succeed but always crash afterward with Bun segmentation fault (v1.7.0)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 279
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 114
Description
CLI version
1.7.0 ============================================================ Bun v1.3.14 (0d9b296a) Windows x64 Windows v.win11_dt CPU: sse42 avx avx2 avx512 Args: "C:\Users\km4721\AppData\Local\sonarqube-cli\bin\sonar.exe" "--version" Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc standalone_executable exited Builtins: "bun:main" "node:async_hooks" "node:child_process" "node:constants" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:process" "node:readline" "node:stream" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "node:diagnostics_channel" Elapsed: 189ms | User: 109ms | Sys: 125ms RSS: 106.50MB | Peak: 106.50MB | Commit: 0.29GB | Faults: 28531 | Machine: 33.59GB panic(main thread): Segmentation fault at address 0x2DF9BEE5692 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: https://bun.report/1.3.14/w_10d9b296kggQugggCCiBATT_HelperApi.dll0g1JCiBATT_HelperApi.dll8hmoBCcKERNELBASE.dll2nyvBCYQIPCAP64.dll6+0ICYQIPCAP64.dllq/wFCYQIPCAP64.dll4viICYQIPCAP64.dll4kvLCSntdll.dll0mw3CCSntdll.dllmy7PCSntdll.dll+z+qBCSntdll.dll8q3qBCYKERNEL32.DLL2rqQkoqBs81rGu9orGqwzwvB8qrwwC_69xy3B_A2+tB920mikD panic: Segmentation fault at address 0x2DF2773C745 panicked during a panic. Aborting.
Operating system and version
Windows 11 x64 (PowerShell 5.1)
Command you ran
Multiple.
sonar --version
sonar --help
sonar system status
sonar update
What happened
On Windows 11, `sonar` commands appear to work, but the process always crashes immediately afterward with a Bun segmentation fault panic.
panic(main thread): Segmentation fault at address 0x2DF9BEE5692 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: https://bun.report/1.3.14/w_10d9b296kggQugggCCiBATT_HelperApi.dll0g1JCiBATT_HelperApi.dll8hmoBCcKERNELBASE.dll2nyvBCYQIPCAP64.dll6+0ICYQIPCAP64.dllq/wFCYQIPCAP64.dll4viICYQIPCAP64.dll4kvLCSntdll.dll0mw3CCSntdll.dllmy7PCSntdll.dll+z+qBCSntdll.dll8q3qBCYKERNEL32.DLL2rqQkoqBs81rGu9orGqwzwvB8qrwwC_69xy3B_A2+tB920mikD panic: Segmentation fault at address 0x2DF2773C745 panicked during a panic. Aborting.
What you expected to happen
Each command should complete and exit cleanly with no panic/segmentation fault output.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing sonar --version, sonar --help, sonar system status, and sonar update on Windows 11 x64 with Bun v1.3.14 and PowerShell 5.1. Compare the command output and exit behavior with the reported segmentation fault; done means each command completes and exits cleanly without panic output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, typescript
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100