I have a macro running and it does a bit of effects, export the tracks, save the project and then close it using python and 40% of the first time it will crash but 100% of the second time it will crash I can constantly recreate the crash if that helps.
My system specs: Intel i9-9900k, RTX 3080, 32GB RAM.
Here is the crash report:
crash.txt (126.7 KB)
This is my first-pass impression, not thinking about it too much.
The first time, you overload the machine part way through the procedure and it falls over. The second time, you try to run the machine with it already overloaded. 100% crash.
Every time Audacity performs an edit or most other actions, it makes a safety copy of The Whole Show. If you need to Edit > Undo for any reason, Audacity doesn’t try to unscramble your last edit. It just plays back the last show.
If you have a long show and your Macro performs a bunch of operations, you could fill up the system in no time.
This could be made worse by using drives outside the computer. Audacity doesn’t like outside drives. It might tolerate close-in USB or Lightning connected drives, but the instant you graduate to Home Network drives, all bets are off.
Audacity naturally assumes it can perform any activity, no matter how critical or delicate on any drive it can see.
The silly example is trying to set up for a critically timed, multi-track, music overdubbing session with an internet-connected drive in a machine facility several time zones away. So not happening.
Koz