I had the most amazing jam last nigh, but this morning, Rack won't open.

VCV Rack
1

Hello

So I had a toot and it might have not been “The Most Amazing” jam, but it was pretty damn cool. Today I tried to open the project and now Rack 2 itself will not open ANY project. I even re-downloaded Rack but same issue. I can perhaps post the project? Not sure how to do that. Anyway, any troubleshooting tips would be appreciated.

Edit - as a further measure I shut my computer down and restarted it. Upon launching Rack I get the “Rack crashed / buggy” message. If I say I say clear patch and start over it opens but I cannot open a project. If I say no it crashes.

Edit and deleted a message,

Further edit - and Rack is now killing Ableton if I try to open a project where Rack is a VST.

2

check log file in user Rack dir before restart, right after crash (at startup it seems) to see what causes Rack to crash exactly.

3

Sometimes deleting the files in the “autosave” folder will help.

afbeelding

4

I have a list of 9 numbered files in Autosave in a file called modules, all dated the same November 11/22, all apparently empty. And oddly, I have one Max for Live patch in there as well which I will delete. But no, same issue, when I try and open it I get the “Rack crashed last time” message and if I choose not to clear it Rack simply doesn’t open. If I clear it I get an empty rack.

5

Where might I find this? I do not see a Rack 2 folder in my User AppData Local or Roaming files…

6

In your documents ?

7

image

“Open user folder” will show you where your user folder is located.

1 Like
8

Ah… the log - Notepad file I take it. Didn’t really even notice it there before. Not that I know what it all means. Nothing stands out as an error. There’s no time stamp on any of these lines to match it up to when this occurred.

9

it gets rewritten every time you start Rack. So post it after a ‘not start’ (crash at startup)

2 Likes
10

And, to be clear, the expectation is that right at the end of the log there will be an obvious crash stack. This isn’t guaranteed 100%, but it’s usually the case.

11

Interesting. Okay, I tried opening the project in question again and the following is the last 21 line items:

[2.983 info src/engine/Module.cpp:173 fromJson] Patch created with RPJVisualizer 2.1.6, currently using version 2.1.10. [3.461 fatal adapters/standalone.cpp:49 fatalSignalHandler] Fatal signal 11. Stack trace: 18: 0x0 17: 0x0 16: _C_specific_handler 0x7ff892c67f60 15: _chkstk 0x7ff892dd2300 14: RtlRaiseException 0x7ff892d81070 13: KiUserExceptionDispatcher 0x7ff892dd0f20 12: strlen 0x7ff892c9d2c0 11: ZN9LFMModule12dataFromJsonEP6json_t 0x7ff836054990 10: ZN4rack6engine6Engine8fromJsonEP6json_t 0x7ff847e37fd0 9: ZN4rack5patch7Manager8fromJsonEP6json_t 0x7ff847de7400 8: ZN4rack5patch7Manager12loadAutosaveEv 0x7ff847de77a0 7: ZN4rack5patch7Manager10loadActionENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8c50 6: ZN4rack5patch7Manager6launchENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8ea0 5: ZN4rack5patch7Manager6launchENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8ea0 4: ZN4rack5patch7Manager6launchENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8ea0 3: ZN4rack5patch7Manager6launchENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8ea0 2: ZN4rack5patch7Manager6launchENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 0x7ff847de8ea0 1: BaseThreadInitThunk 0x7ff892a47600 0: RtlUserThreadStart 0x7ff892d82680

Apologies that this doesn’t look quite as orderly as the log in Notebook - and even in the post window.

12

Are you sure you have tried deleting the autosave file?

13

Just tried it again - deleted the autosave file entirely, not just the contents. Got the same results - here is a screen shot of the above so it’s more ordered.:

image
image986×451 10.7 KB

Have to run for groceries… Quick edit - the Autosave file comes back with the same “modules” file that has 9 empty numbered files in it. There is also this “patch” module of a type called Max JSON.

14

line 11 looks like a data parse of a json for a module index.

15

Maybe remove the RPJVisualizer folder from the plugin folders and try to start Rack again ?

afbeelding
afbeelding946×216 10.7 KB

16

yes, crash certainly seems to be there. @robert.kock - any of this look familiar?

17

I think if you put three ticks around it, it looks better?

[2.983 info src/engine/Module.cpp:173 fromJson] Patch created with RPJVisualizer 2.1.6, currently using version 2.1.10. 
[3.461 fatal adapters/standalone.cpp:49 fatalSignalHandler] Fatal signal 11. Stack trace: 
18: 0x0 
17: 0x0 
16: _C_specific_handler 0x7ff892c67f60 
15: _chkstk 0x7ff892dd2300 
14: RtlRaiseException 0x7ff892d81070 
13: KiUserExceptionDispatcher 0x7ff892dd0f20 
12: strlen 0x7ff892c9d2c0 
11: ZN9LFMModule12dataFromJsonEP6json_t 0x7ff836054990 
10: ZN4rack6engine6Engine8fromJsonEP6json_t 0x7ff847e37fd0
18

No doesn’t look familiar. But definitely caused by my module. Only thing, how can we get this crash if there is no autosave file? It says patch created with… . So looks to me like it is trying to load a default patch that already contains my module . And it is configured for an old version of the module. I have to check why it is conflicting.

19

I don’t believe the RPJ Visualizer is the problem, it just happens to be the last item in the list prior to the line that has the …“Fatal signal 11. Stack trace:”

Some of the others above it:

image
image1225×632 74.9 KB

20

Did you try to delete the folder like @Yeager suggested? Just to see what happens?