I recently updated to Audacity 3.6.2 and it crashes when I click “X” to exit the program after using it for some time (just to split a single WAV into tracks). I receive an error window with the option to report the crash, but the “Send” option always fails.
Are you using drives other than the computer internal drive? Audacity doesn’t like that very much.
Every time you do an edit or any change, Audacity makes a copy of the whole show. That’s how it does Edit > UNDO. It may have started out a simple, one-track show, but internally Audacity has created multiple copies, one for each edit.
From what? You can step back to earlier versions of Audacity if you run into problems.
When you get the older one installed, there is a first-level clearout.
Tools > Reset Configuration
If it’s still misbehaving, then you may need to do a more serious reset.
Stepping back is recommended because Audacity 3.6.2 was designed to help crashing problems. Stepping back may be the fastest way to return to production while the developers resolve this.
Thanks for the reply, koz – I respond individually below.
OK. I think it probably would better if it didn’t do that…
I guess what you meant is that this is already known and being worked on?
In any case, my post here is just to manually report the “crash on close” error, as the automated tool fails to do so (two simultaneous errors!).
Yes, though I believe Linux (e.g. Ubuntu) typically has an “X” to exit a program in the upper-right corner too. I didn’t know Mac OS didn’t have that. My specific OS details are in the log file, if useful.
That makes sense. I briefly saw a window which said something like “Deleting edit history” or something like that upon closing the program.
3.6.1
Thanks for the suggestion. I have considered it, especially since I seem to be running into random problems on recent versions (0 dB line disappearing, spectrogram zoom not working, old custom EQ curves no longer accessible, etc), but they seem to all get resolved by the hard-working developers, so for now I try to stay up-to-date as much as possible just in case any security flaws were fixed etc. I might roll back to the old 2.x.x if I get frustrated, but for now everything is working okay.
Anyway, thanks again for the reply & I hope the crash report is helpful.
I have just updated to 3.6.3 and Audacity still fails to exit cleanly, producing a Problem Report which fails to send as reported by other users. On re-start I get a Recovered Projects box offering the last autosaved session(s). Running on Windows 11 Home 23H2 build 22631.4169 on AMD Ryzen 7 3700X. Is there an address where I can send a copy of the next Problem Report?
Running Windows 10 Pro Version 22H2 and updates to 14 Sep 2024
I am experiencing a closely related problem with 3.6.3. Having saved the project as well as exporting the file I am working on where clicking on Close Audacity exits and gives the following attached error report. Also, on reopening Audacity, I get a recovery pop-up option. I have also attached a log file of dll files not being found.
I’m getting the same thing with Audacity 3.6.3; older versions never did this. I wonder what changed and what the Audacity team is doing to fix it. I never save my projects and haven’t in any of the Audacity release versions.
“Exception Code 0xc0000005.
Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0x6af
Process uptime: 2669 seconds”