Now you just have to make it crash 
Hello Cabbage falls very often. Any suggestion?
OK - I did it again:
https://drive.google.com/file/d/1_qd5leSEBiDTQxKrW2v02lrv_EFWHsul/view?usp=sharing
At about 7:00 I clicked on the ‘Edit Plugin’ button and it crashed. It was playing before but that is not the reason. In a later session I tried to go to edit with the instrument playing and vice versa starting the instrument while the widget window is in edit mode several times and it did not happen.
I also asked myself why I was in play mode although I only wanted to rearrage the widgets in that session. In another session, here:
https://drive.google.com/file/d/1PSXxVkPnGEUuht1scU-xePzV7U9AylfZ/view?usp=sharing
I noticed that sometimes hitting the edit button (You even see the popup help showing that I clicked in the right place at 1:09.) activates playing.
This should happen all the time. If you are not in edit mode Cabbage assumes you are in play mode. I still can’t recreate your crash.
I’ll keep trying to recreate the issue here, but you have no reason to go to edit mode unless you are using the GUI editor. I rarely enter enter mode at all. I simple edit the GUI code and hit save. It’s not a fix, but might help prevent crashes for you only edit the GUI via code?
That’s actually how I started using it. I never used the edit window to move items with the mouse. When the first crashes appeared I suspected that they happened when csound is called every time I just want to see the widget arrangement. To avoid this I started using the edit mode if I just wanted to change the widget arrangement and not play the instrument - without avail.
One thing I tried is to run cabbage as admin just in case some of the files on my computer don’t have the correct permissions and that makes it break. But I still get crashes.
Is there anything like a dump created when it crashes? At least a window pops up that it will send some information to Microsoft. But it is not like on a Mac that the system shows me that information. But it must be present somewhere and it may give some clue.
Meanwhile, I have the feeling that there must be something wrong with my Windows system, drivers or interfering software installed. But since the crash happens at random times I have no idea what it is actually related to. Are there any dependencies on pre-installed libraries on Windows?
Good idea about the backteace. I’ll try to prepare a special build that will give us more info when Cabbage crashes. 
Hi @RZorn, can you try this exe when you get a chance. You should probably just rename your current Cabbage.exe and use this one in its place. If Cabbage crashes it will produce a stack trace in the Cabbage root folder called CabbageDump.txt. It doesn’t give the fullest of stack traces, but should be enough to point us in the right direction.
Where did you put the exe?
Just now I had a crash with the alternative exe installed. I fear the crash happens in a way that no dump is produced. I looked into C:\Program Files\Cabbage and to be safe did a search of any .txt file changed today. CabbageDump.txt did not show up.
I did some background research how Windows documents crashes. The Reliability Monitor shows
Das Programm Cabbage.exe Version 2.5.16.0 hat die Interaktion mit Windows beendet und wurde geschlossen. Überprüfen Sie den Problemverlauf in der Systemsteuerung “Sicherheit und Wartung”, um nach weiteren Informationen zum Problem zu suchen.
Prozess-ID: 5b4
Startzeit: 01d70dae32f2b997
Beendigungszeit: 6
Anwendungspfad: C:\Program Files\Cabbage\Cabbage.exe
Bericht-ID: c3c63ed5-211c-4073-9373-8fbdb3524bae
Vollständiger Name des fehlerhaften Pakets:
Relative Anwendungs-ID des fehlerhaften Pakets:
Absturztyp: Unknown
(Unfortunately that gets translate into German. I hate localisation!) But the last line means ‘crash type: unknown’, so it seems not to be that helpful…
The event viewer does not show much more:
Protokollname: Application
Quelle: Application Hang
Datum: 28.02.2021 10:08:20
Ereignis-ID: 1002
Aufgabenkategorie:(101)
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: PC-2020
Beschreibung:
Das Programm Cabbage.exe Version 2.5.16.0 hat die Interaktion mit Windows beendet und wurde geschlossen. Überprüfen Sie den Problemverlauf in der Systemsteuerung “Sicherheit und Wartung”, um nach weiteren Informationen zum Problem zu suchen.
Prozess-ID: 5b4
Startzeit: 01d70dae32f2b997
Beendigungszeit: 6
Anwendungspfad: C:\Program Files\Cabbage\Cabbage.exe
Bericht-ID: c3c63ed5-211c-4073-9373-8fbdb3524bae
Vollständiger Name des fehlerhaften Pakets:
Relative Anwendungs-ID des fehlerhaften Pakets:
Absturztyp: Unknown
Ereignis-XML:
1002
0
2
101
0
0x80000000000000
1821
Application
PC-2020
Cabbage.exe
2.5.16.0
5b4
01d70dae32f2b997
6
C:\Program Files\Cabbage\Cabbage.exe
c3c63ed5-211c-4073-9373-8fbdb3524bae
Unknown
55006E006B006E006F0077006E0000000000
That’s odd, thanks for testing though. Tomorrow I will prepare a new build that you can crash on purpose just to see if we can produce the dump txt. I’ll add some bogus code just for testing purposes. That’s how I was testing it here…
Can you try this one? I have added a special menu command under ‘Tools’ to crash Cabbage (this might be a first in the history of software development!) 
Anyhow, if you trigger that, can you check your Cabbage root folder and see if it generated a .txt file for you with the strack trace? Thanks.
Sorry, it did not produce a txt file. (I also checked by a file search on the whole drive.)
Also the crash is different from that I usually experience. Usually, Cabbage gets unresponsive and the actual crash is probably induced by chosing the option ‘terminate’ in the window opened by the system. That is also what is recorded in the reliability monitor. But for the deliberate crash there is no record in the RM.
So when you try the menu command to crash the application it doesn’t produce a .txt file in the same directory as the Cabbage.exe file? I can’t understand how this is the case. Does it at least crash the application?
Yes, it does crash the application. But it does so immediately, while the random crashes occur after the application is identified as ‘unresponsive’ by the system.
And in this instance does it create a stack trace text file? At this point I’m just wondering if my stack trace function is being called at all?
How could I overlook this: I am usually not working with admin privileges. But the programs/cabbage directory was created just with read permission for ordinary users. So it could never write anything. I granted the write permission and the deliberate crash produces the file. Waiting for the unepected one now.
Oh great. Bloody Windows
The good news is that from the time since my last post you can see that the crash doesn’t happen so often. The bad news is that it did just now and did not write the dump. What I think is that Cabbage actually does not crash but hangs in a loop. And when Windows terminates Cabbage (on my request) it does not enter the dump routine.
Actually, if that happens again, can you right-click the “Cabbage (not responding)” process in the task manager and select create dump? That’s even better 
Finally, it happened again and here is the dump: https://drive.google.com/file/d/1JVkDeCJNB5UcvHVhqnFZJ3026o-71m0C/view?usp=sharing