Installed 3.6.1 over or on top of 3.6.0 and it gave “mem exception error” twice while recording. Didn’t get a screengrab. I was too infuriated.
System is Win10 all latest updates, HP Z600 Workstation, K4000 GPU.
See this known and logged bug that Muse are endeavouring to fix for the upcoming 3.6.2 release.
opened 12:28PM - 02 Aug 24 UTC
bug
crash / freeze
regression
### Stacktrace
```
Operating system: Windows NT
10.0.22… 631 3958
CPU: amd64
family 25 model 97 stepping 2
32 CPUs
GPU: UNKNOWN // nvidia 3090 if that matters
Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x0
Process uptime: 4889 seconds
Thread 0 (crashed)
0 lib-wave-track.dll + 0xf16b
... // rest attached as file
```
### Steps to reproduce
1. launch Audacity
2. set recording channels to 2
3. click Record
4. wait for ~1-1.5h
**UPDATE by PS**
<details>
Another simple reproducible use case _(see first comment below in this thread)_
1. clear audacity settings folder (to get OOTB factory default settings)
5. launch 3.6.1 - on W10 or W11
6. Press Record
7. Observe: stereo recording starts
8. Observe: after around 6 hours Audacity crashes and stops recording
_Note that accepting recovery on relaunch safely restores the 6 hours of recorded audio._
**UPDATE by PS**
Note further that when saving an empty project before starting to record, then the crash does not occur. Indiacting that the underlying issue here is with thu use of the temporary files. I have thus edited the bug's title.</details>
### Expected behavior
no crash
### Actual behavior
a crash
### Audacity Version
3.6.0 onwards
### Operating system
Windows
### Additional context
Recording from Xonar U7 MKIII Line-In (USB soundbox by asus), MOTU M2 interface.
Peter