cmajor-lang
CAN NOT Run with VSCode extension
Thanks for implementing such an interesting language! While I follow the guide to install vs code extension, I used one of the examples and try to run by using cmajor tools, but I got following errors. My Mac machine is M2 with OS version 13.5.2. Is there any other requirements?
ERROR DETAILS:
Starting server process at Fri Jul 12 17:09:37 2024 Cmajor Version: 1.0.2562 Build date: Jun 18 2024 22:15:57 OS: OSX
Cmajor server active: http://127.0.0.1:51020
Session created: HFABNSIGIE
| Session | Age | URL | | | | | | HFABNSIGIE | 572 microseconds | http://127.0.0.1:51020/session_HFABNSIGIE/cmaj-patch-chooser.html |
Loading patch: /.vscode/extensions/cmajorsoftware.cmajor-tools-1.0.2562-darwin-arm64/examples/808/808.cmajorpatch Audio API: CoreAudio, Output device: Apple Inc.: xxx, Input device: Apple Inc.:xxx, Rate: 44100Hz, Block size: 128 frames, Latency: 118 frames, Output channels: 2, Input channels: 1 Total build time: 478.83 ms load: 54.97 ms, compile: 33.2 ms, link: 390.65 ms
libc++abi: terminating due to uncaught exception of type cmaj::AbortCompilationException
By the way, I can use cmajor command tools such as cmajor play to run patches successfully.
Hi there - that's very odd, we've not seen anything like that, and we test heavily on OSX. Does it happen with all of the examples, or just one in particular? Anything else unusual about your machine or setup..?
I'm seeing the same thing with v1.0.2562 (on macOS 14.5 / M2) with the default patch that gets generated when running "Create a new patch" from the extension.
Figured out that disabling Bluetooth on my mac fixes the problem for me.
I can reproduce the issue by turning Bluetooth back on, and then waking up my iPhone so that its microphone appears as an available audio input as part of the Continuity Camera feature.
If I then try to run the patch using the extension I see the same exception in the output again:
libc++abi: terminating due to uncaught exception of type cmaj::AbortCompilationException
Hi there - that's very odd, we've not seen anything like that, and we test heavily on OSX. Does it happen with all of the examples, or just one in particular? Anything else unusual about your machine or setup..?
I tried to change version of extension, but it didn't help. Also tried the bluetooth and input/output devices, the same issue. Could you imagine any configuration will cause such compile error? Or where could us find the detail error message?
Every cmajor patch will meet this problem when rendering using html with vs code extension and the local binary executor. Maybe the web html is the problem?
I checked it with some of my friends' Mac machines, also faced this problem when using latest vscode extension to render with web, both in x86 and arm64.
I found the key casue of this issue, the language of the system will affect serialization of json, the serialization of json wil fail if it faced non-ascii characters like chinese words. When I switch my system to English version, it works.
We have updated to resolve some non-binary mode file logic, can you check whether you still have this problem with the latest version? We tried to recreate the issue but failed, so sorry if we've not managed to catch the exact place this happens
Using v1.0.2662 of the VSCode extension and still appear to be hitting the same issue. I can workaround it by renaming the iPhone to remove the ’ character, after which patches will run successfully.
I confirm that the name of my iphone as an input device on Mac OS was the cause of the same crash. It was seen as Iphone "de Michel" and the " is certainly the cause of the crash.
I've experienced this issue; running a new GUI patch (straight from new GUI patch template, no edits) gets me "Lost connection to the Cmajor server process!" and the following output:
------------------------------------------------
Starting server process at Thu Dec 26 11:01:03 2024
Cmajor Version: 1.0.2747
Build date: Nov 28 2024 21:29:27
OS: OSX
Cmajor server active: http://127.0.0.1:51020
Session created: BJOCTWHTFY
----------------------------------------------------------------------------------------------------
| Session | Age | URL |
| | | |
| BJOCTWHTFY | 59 microseconds | http://127.0.0.1:51020/session_BJOCTWHTFY/cmaj-patch-chooser.html |
----------------------------------------------------------------------------------------------------
Loading patch: /Users/<ANONYMIZED>/JUCE_Programs/C_Major/Tuto.cmajorpatch
Audio API: CoreAudio, Output device: Apple Inc.: External Headphones, Input device: Apple Inc.: External Microphone, Rate: 44100Hz, Block size: 128 frames, Latency: 114 frames, Output channels: 2, Input channels: 1
Total build time: 41.22 ms
load: 11.57 ms, compile: 12.42 ms, link: 17.23 ms
------------------------------------------------
libc++abi: terminating due to uncaught exception of type cmaj::AbortCompilationException
------------------------------------------------
The problem goes away when I disable the Bluetooth; comes back when I turn BT back on.
I am also getting this error - rather annoying when you simply want to check out some examples.
The error goes away when shutting down BT.
I am trying to get the apostrophe out of my iPhone's name now...
had to restart my Mac for that change to propagate, error's gone
Disconnect the microphone of your iPhone if you are using Mac OS. Sometimes this device name contains quotes or strange chars that raise this error.
Le jeu. 19 juin 2025 à 15:31, Steven Kruyswijk @.***> a écrit :
crosswick left a comment (cmajor-lang/cmajor#72) https://github.com/cmajor-lang/cmajor/issues/72#issuecomment-2988112929
I am also getting this error - rather annoying when you simply want to check out some examples.
The error goes away when shutting down BT.
I am trying to get the apostrophe out of my iPhone's name now...
— Reply to this email directly, view it on GitHub https://github.com/cmajor-lang/cmajor/issues/72#issuecomment-2988112929, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE6LWAPCYX7LWD75TPYA2T3EK3UDAVCNFSM6AAAAAB7V6IKGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBYGEYTEOJSHE . You are receiving this because you commented.Message ID: @.***>
Just to let you know, i've finally tracked down a fix for this, and the latest VSCode release includes this fix. Can you try this and confirm it is now working.
Ok, i'll assume it is now fixed, please open a new ticket if you see this problem again!