Windows Bug Reports — What I've found so far (with tracking sheet)

Cabbage 3
1

Hi Rory & fellow Csounders! :waving_hand:

I’ve been diving into Cabbage 3 from Lima, Peru — documenting my experience as I go, partly for myself and partly for my students at the Instituto Orson Welles.

I’ll use this thread to report Windows-specific bugs and issues I encounter along the way. Nothing fancy, just real-world findings with logs, causes and solutions when I can find them.

To keep things organised I’ve put everything in a community tracking spreadsheet (English + Spanish) that anyone can copy and use:

:bar_chart: [Cabbage 3 — Known Issues & Solutions — Google Sheets link here]

To get your own editable copy: File → “Download” or “Make a copy”

I’ll post each issue as a reply below. Hope it’s useful!

Julio

2

BUG #1 — Crash 0xC0000005 on startup (incompatible Csound7 version)
Version: vscabbage 1.0.184-alpha through 1.0.187-alpha
OS: Windows 10/11
Csound installed: 7.0.0-beta.13 (Nov 10 2025) ← incompatible
Csound required: 7.0.0-beta.15 (Mar 9 2026) ← works
Date confirmed: 2026-03-20

Symptom:
CabbageApp.exe exits immediately after attempting to load a .csd file. The UI never opens in VS Code. The server starts correctly but crashes as soon as it tries to initialize Csound.

Error code: 0xC0000005 (Access Violation) — Windows exit code 3221225477

Log:

Csound SetHostData: enginePtr=...
=== CABBAGE PROCESS EXIT ===
Exit code: 3221225477
Signal: none

Root cause (confirmed via Windows Event Viewer):
The crash occurs inside csound64.dll. Event Viewer shows:

Faulting module name: csound64.dll
Faulting module path: h:\Program Files\Csound7\bin\csound64.dll
Exception code: 0xc0000005
Fault offset: 0x0000000000043104

CabbageApp loads the system Csound7 DLL from the PATH. If that DLL is from an older beta (Nov 2025), it is API-incompatible with Cabbage 1.0.187 and causes an immediate Access Violation inside setupCsound.

Misleading symptoms that distracted from the root cause:

  • Multiple virtual audio devices (VoiceMeeter, VB-Audio) were present and suspected
  • RtAudio: no compiled support for specified API argument appeared in logs (this is a benign warning, not the cause)
  • Disabling virtual devices did not fix the crash

Solution:
Update Csound7 to 7.0.0-beta.15 (Mar 9 2026) or later. After update:

--Csound version 7.0 (double samples) Mar  9 2026
[commit: 973089dce54ec2695e4df144c44e4333991634eb]

Download from: Releases · csound/csound · GitHub

Suggestion for Rory:
Could Cabbage check the Csound7 DLL version/date on startup and show a clear error message if it’s incompatible, rather than crashing silently with a Windows Access Violation? This took several hours to diagnose.

3

BUG #2 / FEATURE REQUEST — UI does not open when no audio device is available

Version: vscabbage 1.0.181-alpha
OS: Windows 10/11
Csound: 7.0 (Feb 7 2026)
Date confirmed: 2026-03-20

Symptom:
The Cabbage server starts and Csound compiles the .csd correctly, but the UI tab never opens in VS Code. No crash, no visible error to the user — it just silently fails to show the interface.

Log:

ERROR: No audio devices found! [CabbageAudioApp.cpp (687)
CabbageAudioApp::initialiseAudio Thread ID: 23536]

(appears three times consecutively)

Cause:
No audio device was available — neither physical nor virtual. The Cabbage server cannot complete initialization without audio, leaving the WebSocket connection to VS Code unestablished. Csound compiles and runs internally but the UI is never served to the VS Code tab.

Current behavior: Clean error, no crash — which is good. But the user receives no feedback in VS Code explaining why the UI didn’t open, making it very hard to diagnose.

Solution:
Connect any audio device before starting the Cabbage server (USB headphones, audio interface, etc.).

Feature request:
Would it be possible to allow the UI to open in a silent/dev mode even without an audio device? This would be very helpful for pure UI development workflows where audio output is not needed at that moment. The Csound compilation works fine — it’s only the UI serving that fails.

4

Thanks @F7h for these reports. I will take a look and try to implement your suggestions. Please keep them coming, there are not many people trying Cabbage 3 yet, so it’s great opportunity to kill these bugs before more people come onboard :slight_smile:

Btw, with regards to the first issue, once Csound 7 is officially released, the versions shouldn’t be so important anymore, so long as it’s an official version 7. While 7 is under development, things are changing internally that are causing some compatability issues.

5

Hi @F7h I pushed an update for the second issue but I can’t test as I don’t have a device with no audio interfaces. Maybe you can try it out when you get a chance.

Regarding the first issue, this one isn’t so simple. The problem is that the current Csound betas don’t include patch numbers, so all get as a version string is 7.0.0, no matter which beta it is. There are ways to protect against the crash, but they are a lot of work to implement for an issue that will disappear once an official release is made. In the meantime I’ve updated the readme that shows when you click on the Cabbage vscode extension in vs code so that is provides the exact version of Csound Cabbage was built with. I hope that’s Ok for now :+1:

6

Fix confirmed :white_check_mark: — vscabbage 1.0.188-alpha, Csound 7.0.0-beta.15 (Mar 9 2026), Windows 10

Tested on a student PC with all audio devices disabled. The UI now opens correctly without any audio device. Csound compiles and the interface loads — only audio output is unavailable, which is exactly the expected behavior for a dev/UI workflow.

Great fix Rory, thank you! :leafy_green:

Julio

20260328123448.txt (3.9 KB)

1 Like