App version: Audacity 2.4.2 and 3.0.2 for Windows (clean, fresh install)
OS version: Windows 10 Enterprise (64-bit), Version 10.0.19041 Build 19041
Memory: 32GB RAM (but also happened while I was on another system with 16GB around 3 years ago)
Steps to reproduce:
- open 36 windows/projects in total (e.g. start Audacity and then additionally press Ctrl-N (or choose File/New) 35 times more) → it’s ok
- open one more window/project (37th):
- Audacity 2.4.2 goes into “Not Responding” state (also seen in the window title bar), use Task Manager or click X to force close it
- Audacity 3.0.2 just disappears (gets closed, but no info box from Windows that the app crashed)
Of course, this doesn’t happen just with empty windows/projects, but also with ones containing track(s), active work and so on…
In that case when there’s content in each window/project and Audacity hangs, you close Audacity, restart it, then AutoRecover kicks in asking if you want to recover what it found present on the file system, you choose Recover, it start to open past content and brings back Audacity windows/projects 1, 2, …, 37 → auto stuck again.
To fix this AutoRecover case for example either choose Discard everything on re-open or just move (or delete) 1 .autosave file away from
C:\Users<username>\AppData\Roaming\audacity\AutoSave\ and it should at least be able to start up again and AutoRecover at least N-1 (36) projects.
Related to a previous report?
Sounds similar to https://forum.audacityteam.org/t/automatic-crash-recovery/26102/1 from 2012, at least the number of windows/projects and behaviour.
If the approach for this one is “just don’t overdo it” then nevermind…