I edit audio once a week at my office. For the fourth week in a row, I’ve gotten this exception code upon exit (after saving my project, exporting audio, and being asked if I want to save my project upon exit [yes]). The Problem Report for Audacity window pops up, but when I click [Send] I get an error “Failed to send crash report”. Same error occurs if I attempt to send the crash report again.
The first week I simply clicked [Don’t send] and went about my business, but the second week when I opened Audacity there was a file to recover. I recovered it, then did my weekly audio editing. Same error occurs each week upon exit. Same error occurs when I try to send the report. Each time now I copy the text of the Problem Report and save it (in case it can be sent some other way).
This week (5/21), I saved my project, then exited Audacity before exporting the audio from my project. The exception code error recurred as before.
I’m running Windows 11 Home on a fairly new computer (less than a year old). There are 702 GB free on the data hard drive, and it is optimized weekly by the operating system.
I believe this error has occurred every time I’ve edited audio with this latest version of Audacity (3.5.1), but I’m not 100% sure of that. If there’s some place I can send these error reports I’ll gladly do it.
I’ve just experienced exactly the same behavior with Audacity 3.5.1 on Windows 11. When I attempted to open the aup3, I had to recover it. Closing after that happened without an error, as did reopening and closing again. I’d post the error log, but I don’t see how to do that. I’ve used Audacity for many years without an issue, and I don’t think I’ve had a problem in 3.5.1 before now. Windows 11 has been updated as Microsoft decides to, so there has certainly been an OS update since the last time I used Audacity.
It’s nice to know I’m not the only one experiencing this! It happened again today. At least it doesn’t seem to be affecting exported audio files, and my original audacity files seem fine once they are recovered.
But it’s certainly an annoying extra couple of steps each week!
Hopefully we’ll get some answers soon from Audacity.
Well, this exception also occurs under Windows 10. I am curious if and when there will be a solution. As the sending of the debug data does not work, I copied the entire text to a text file - just in case. Is there a place to drop this information off?
Sorry you have joined the group of users experiencing this!
I, too, have been saving the debug data to a text file each week when I get the error again. As none of the Audacity staff have replied, I know of no place we can send this data in order to facilitate a solution.
We can only hope that Audacity staff will soon reply.
I just upgraded to 3.6.1, hoping that it would solve the problem. I edited a new sound file today, then exported the audio to my computer and exited Audacity.
Sadly, it doesn’t fix the error. It didn’t even solve the error report failure, so I saved the error information yet again. sigh
I don’t see a way to change my title so I can indicate the problem is continuing in 3.6.1.
Audacity staff, are you seeing this problem report? Can it be escalated, please?
Are y’all using network, external, or cloud drives? Audacity hates that.
The latest “Cloud Saving” thing doesn’t count. That is a special purpose service on audio.com and only used for Audacity Projects.
I think I would decelerate back to Audacity 3.4.2 and then Tools > Reset Configuration. See how that goes.
Get the older Audacity from here.
If you have crashes on Windows, you should do a clean shutdown to sweep away broken file fragments. If you don’t, the fragments will make further crashes more likely.
Kozikowski,
I’m using a hard drive on my computer, not a network, cloud, or external drive.
Windows itself is not crashing, just Audacity. I’m not sure what you mean by a “clean shutdown”. I shutdown my computer every time I leave the office, so if that’s what you are meaning it doesn’t apply to this issue.
I don’t have time this week to try installing an old version of Audacity. Perhaps next week.
Good start. The cloud people go to a lot of effort to make their cloud offerings “look like” a regular internal drive.
To be clear, Audacity thinks any drive it can see can be used for any job, no matter how delicate, critical, or difficult. Suddenly discovering that your tightly-controlled musical overdubbing job is being managed from a cloud drive outside of Schenectady is not good news. Blammo!
Nobody wants to wait for Windows to “start over” each time it, well, starts over. So Windows leaves portions of itself running, set up, or in “hibernation.” That’s fine as long as nothing ever goes wrong. The first time you have a crash or other serious problem, it may leave shards and trash over the system which a quick, convenient shutdown may not catch. This can lead to more frequent or deeper crashes.
That’s not the only way to do that. Search for “Clean Shutdown.”
Audacity problems started in the 3.5 series and have been getting far worse as the versions progressed. Stepping up to the latest version is not going to solve all your problems. The Audacity 3.6 series destroyed several of the Audiobook production tools which I am scrambling to rewrite.
I’ve been having the same issue for a long time now. Nothing anyone has suggested has fixed it. It started in the middle of editing an audiobook. Several times I thought i had uploaded clean exports but because of constantly having to recover files my debreather tool had been moved all over the flipping track, I am so very done with audacity because of this issue. Just about every time i close audacity it fails to close properly and i have to recover the track.
I am using a new computer with a fresh intall of windows. Besides firefox the only other thing i installed on here was audacity to get it set up for work.
Crash report states EXCEPTION_ACCESS_VIOLATION_READ if that helps figure out why this is happening.