Cabbage server terminated with non-zero exit code: 3221225781

Cabbage slugs
1

When I try to start the Cabbage server from VS Code on a PC I get the error below. But the validation did not find any problems. (I still have Csound 6 on another directory, but as I understood from one of the last posts, both should be able to run in parallel now.)

I don’t know exactly when this started but it may be related to the upgrade from alpha to 3.0.20-beta.

=== CABBAGE PROCESS EXIT ===
Exit code: 3221225781
Signal: none
Process ID: 16708
Command: c:\Users\Reiner\.vscode-insiders\extensions\cabbageaudio.vscabbage-3.0.20-beta\src\CabbageBinaries\CabbageApp.exe
Cabbage server terminated with non-zero exit code: 3221225781
=== END EXIT ===
Cabbage installation validation
=================================
✓ [PASS] Csound installed
    Found C:/Program Files/Csound7/bin/csound64.dll
✓ [PASS] Cabbage Server
    Found public Cabbage Server: c:\Users\Reiner\.vscode-insiders\extensions\cabbageaudio.vscabbage-3.0.20-beta\src\CabbageBinaries\CabbageApp.exe
✓ [PASS] Cabbage Server is executable
    Not applicable on Windows
✓ [PASS] Cabbage backend settings file (C:\Users\Reiner\AppData\Local\Cabbage\settings.json)
    Settings file exists, is valid JSON, and has a `currentConfig` section
✓ [PASS] JS source directories exist
    1 directory configured, all exist
✓ [PASS] Primary source is the bundled extension
    Primary source matches bundled extension: c:/Users/Reiner/.vscode-insiders/extensions/cabbageaudio.vscabbage-3.0.20-beta/src
✓ [PASS] Widget sources resolvable
    Found 22 widget descriptors in c:/Users/Reiner/.vscode-insiders/extensions/cabbageaudio.vscabbage-3.0.20-beta/src/cabbage/widgets
✓ [PASS] No stale legacy settings file
    No legacy settings file present

Result: healthy — no issues found.
2

Thanks @RZorn I just noticed that myself when trying to fix your other issue. I think a push I made to the repo last week messed this up. I’ll take a look now and try to get a fix asap.

3

Can you try the latest official release of Csound for Windows. I had to update to get it working on my PC. Cabbage is built against the first release of Csound 7, any earlier version, even one of the betas will break it. From hereon in however, you should be able to update freely without anything breaking.

4

FWIW, this was the issue. Csound7 has a new binary name, csound7_64.dll - I’m updating the test to look for this dll name rather than the csound64.dll which is now tied to Csound 6.

5

Yes, this worked. Now I can do the test for the other issue.

1 Like