When I exit Audacity 3.6.2 as follows, it crashes.
Same same. It doesn’t do it every time and I haven’t been able to discern what I’m doing when it does crash. Seems arbitrary.
Audacity programmers, please prioritize stability before features.
I cannot reproduce that crash given your steps to reproduce I’m afraid. On my system it closes just fine.
We’ve done nothing but fix bugs for the last month and a half, as far as Audacity 3.x development is concerned.
See this issue I logged a few days ago:
Peter
Hey there - on a Mac here running Sonoma 14.6.1, and the latest Audacity and same thing happening here. Am sending automated reports with the crashing but it’s every time.
And I will add, it does seem consistent with 3+ tracks to crash … very odd! Hopefully the crash logs help. Thanks so much for the update. Lots of other nice fixes in there.
I just installed version 3.6.2 and it also crashes when I exit the program, often if I type the “X” in the top right. It offers a log but you can’t send it. I attach image
You could not reproduce the crash because you were using a new version of Audacity.
However, those who are experiencing the crash have made settings in Audacity in the past that are a problem in the current version.
If I enter a directory other than the default one under “Preferences: Directories > Temporary files directory”, Audacity 3.6.2 crashes on exit.
I hope this helps.
Since updating to 3.62 Audacity crashes after pressing [Control W} to close project. It generates a crash report but it won’t SEND. Have saved the 2 reports in pdf if anyone wants to see them.
I recorded some cd’s some time ago, and recently returned to the projects to add labels. I updated to 3.6.1 on request. After finishing one project yesterday work I saved the project again, and clicked on Close. When I reopened the file to do an export I received a message saying that I hadn’t closed the file properly and asked me to confirm that the file needed saving. There was Crash Report (?) generated and asked if I wanted it reporting so I clicked that I did, which then get an error report Exception Code 0xc0000005. The file exported okay. Today I worked on another file after updating to 3.6.2 and after saving some work, returned to the file a little later with the same result - hadn’t closed properly. Where am I gong wrong please ?
hey all @here
We can reproduce this thing ourselves now and are working on a fix.
YeeHaw! Excellent.
I had every confidence.
Can’t wait to see it.
I know it won’t fix the crashing issues in Audacity, but for extracting audio from a CD it’s generally faster and easier to rip it than to record it (but check your country’s laws since it’s illegal to rip CDs in some countries, such as the UK). Each CD track will be in a separate audio file so you don’t have to label them.
I haven’t used it (I’m not on Windows), but I’ve seen a lot of people swear by EAC (Exact Audio Copy):
Thanks for the info Christop, but I was so busy trying to get the thread started I forgot that I was recording albums (vinyls in today’s jargon). I have no trouble ripping cd’s on my computer but my Brennan isn’t always happy to do the same !
Funnily enough I have exactly the same problem with my Cocktail Audio X30 mains-powered hi-fi audio file player - so I do the same rip in iTunes to WAV on my PC,
Peter
Same issue for me on Windows 10 (64 bit). But I created a separate thread because I am unable to forward the error report to Audacity.
My directory is correct but still Audacity crashes.
I can confirm this, even with the correct directory the program crashes.
Changing the directory helped me temporarily, but that is not the solution to the problem.
I originally wrote this to give the developers a way to reproduce the crash, not as a solution.
hey @here
This is fixed in 3.6.3.