Just to report it:
updated yesterday to 2.1.31 and had 2 crashes while just editing a new line in a new lyric track, pressed “save” (ctrl/S) on macbook M1 and had a “freeze”.
I hope that it’s fixed with the topic “CRASH during ExportArchive” (fkalmus).
I returned to 2.1.28
again: Thanx to the devs for taking care from week to week!
Hi! I suggest you to attach the crash dump here let developers open and examine it 
(as I personally experienced crash during SaveArchive)
Hi fkalmus,
I would but I simply don´t know how to create/find that “crash dump”.
I had a never stopping “beachball” and just stopped the app.
sorry…any advice?
ohh, if no crash, probably no crash dump. But generally crash dumps are here on OSX:
Ok !
I´ll save that path and try to recreate that error.
maybe there might appear any crash dump file.
Thank you very much!
… that might explain your crash. Are you working with Modules (Focus Control, Viewer, Media Player) too? And have you deleted an instance in your session before you saved your project?
See you,
Michael.
Question:
I had to stop the app by right click on the icon in the taskmenu (bottom of the screen) and then choose “sofort beenden”).
It was not possible to stop it like usual with the menu at the top of the screen…in fact no action was possible.
Is that a “crash” ? …or just a “freeze” or something else…?
Hi Michael,
no…sorry…none of the mentioned Modules.
Just 2 global stacks for vocals and guitar (no plugins…kemper), 2 audio track, a video track and a lyric track, sometimes a chord track.
one screen via hdmi and one screen on an ipad…triggerd by “sidecar” not by viewmod!
that system worked very fine and stable (and does right now). the problem just appeared with the new version (didn´t use 29 and 30 because there were too many bug reports and I didn´t use mediaplayer until now…but I would, if everything runs stable 
)
…but if I remember right…I cut the end of a video track and deleted that end…that´s all…then I started editing the lyrics and at the first “save”…beachball…
It’s a freeze, and it’s very helpful for us when users distinguish between the two. When the app crashes (just disappears, or some message from the system appears), then there is also a crash log, and we are very keen to see those in order to prevent bugs leading to crashes in the future.
A freeze (or lockup, hang, or…) unfortunately cannot produce a crash log. In these cases any information about what you did is helpful.
Probably there is a bug in there, presumably related to this one. Pls check again with the next version, sorry for the inconvenience. You may try if the crash goes away without video just to confirm.
Hi musicullum,
no need for sorrys anyway!
I know that you guys take any problem for serious and solve it fast.
That´s what I really appreciate and that´s what gives me faith to your app!!!
From the beginning up to now there is such an amazing amount of new features…it´s absolutly alright using us to check the new steps …everybody can step back to a stable version.
So…Thank you !!!