cF LABEL crashes VCV rack

I’m on win10x64 and this module crashes vcv rack if i try to insert a text.

Log:

[0.504 info src/main.cpp:189] Starting engine
[0.504 info src/main.cpp:201] Running window
[3.950 fatal src/main.cpp:45] Fatal signal 22. Stack trace:
21: ZN4rack10appDestroyEv 0x456435
20: raise 0x6447ac60
19: abort 0x6447f270
18: assert 0x6447b510
17: osdialog_prompt 0x4a9292
16: ZN9LABELItem8onActionERKN4rack5event6ActionE 0xd00c5a0
15: ZN4rack2ui8MenuItem8doActionEv 0x4a49ae
14: ZN4rack5event5State12handleButtonENS_4math3VecEiii 0x4576c8
13: ZN4rack7updater17isUpdateAvailableEv 0x45914e
12: glfwPlatformUnlockMutex 0x4d78ae
11: CallWindowProcW 0x64235850
10: CallWindowProcW 0x64235850
9: glPushClientAttrib 0x49b13770
8: CallWindowProcW 0x64235850
7: DispatchMessageW 0x64235410
6: glfwPlatformPollEvents 0x4daf66
5: ZN4rack6Window3runEv 0x4594ea
4: main 0x781840
3: main 0x781840
2: main 0x781840
1: BaseThreadInitThunk 0x63557bc0
0: RtlUserThreadStart 0x651aceb0

there is an issue on github since dezember '19 already

1 Like

So what do we do in those cases?

For open-source software like cF, if you need a bug to be fixed, there are a few options.

  • Fix it yourself and attempt to get your patch merged into mainline branch.
  • Persuade or wait for the original developer or another developer to fix it.
  • Pay the developer under an agreement to fix the bug.
2 Likes

Thanks for clarification.