I thought this was fixed in 3.6.3. If I make any changes to a music file Audacity crashes on exit and I can’t send the crash file. I did see something about accessing an illegal address in the crash file.
3 Likes
Are you doing everything on your local drive? Audacity doesn’t much like directly accessing drives outside the cabinet. Starting with close-in USB drives and ending with cloud drives half-way across the state. Don’t do it.
You can move files anywhere you like as long as Audacity is closed.
Maybe I should be paying more attention to that little voice in my head. Are you on Windows and have you ever done a MemCheck?
In the dawning of the video age, people would start editing their video productions at home and many of them started getting odd crashes and other damage—seemingly out of nowhere. Turns out many of them had damaged high memory…
A video edit would go sailing up there looking for room to execute a chroma key or a video motion effect, step on the damage, and BLAMMO, the show would crash.
We get a ton of Audacity crashes for no apparent reason. I may know one reason.
Koz
Likewise, 3.6.3 was still crashing on me and I thought it had been fixed. I do my sound and video editing on a separate hard drive within the cabinet (not on an external drive), but after reading Kozikowski’s response I decided to do a check and move the folder I am currently working on to my C drive. No crashes so far on exit. So, Audacity may be more sensitive than suggested! If it starts playing up again I will repost.
We definitely fixed one way of crashing it, but there may be more. Please try finding ways of repeating the crashes, that would help us immensely.
1 Like
D:\ ??
I hadn’t thought it would be that sensitive to drives natively inside the Operating System. I can put up a good argument for external drive problems. Certainly, network and cloud drives are a nightmare of data management.
Koz
Same with my Winn 11 PC. No other audio or video app crashes.
Yes, the separate hard drive is labelled as D: drive.
However, things are now getting perplexing. After half a day of editing sound files in the folder I relocated to C drive (without problems) I tested some editing in another folder still in D drive and had no error messages on closure/exits. So then I transferred the folder back from C Drive to D drive and after one error message I have been able to continue working in D Drive with no further issues or error messages on exiting/closing files.
So I don’t know what is happening and why. But fingers crossed it may have now settled down on my machine.
Perhaps it needed to be initially used on files in C Drive after installing/updating before being applied to other drives.
I never had any equivalent error messages on my drive configuration until the last two updates.
And I may be premature in saying it is now solved. Time will tell.
That one time it did recently crash (that I mentioned above) occurred when I tried to close the program without saving the file first. It asked me whether I wanted to save it and I said yes (I think). But then I got the error message after the program closed. I haven’t tried to replicate that situation yet.
Here is what I have found on this issue:
First of all, this is on a windows 10 system which I use to edit some rather large .wav files up to 2 hours long. I noticed that the crash on exit in 3.6.3 was dependent on the size of the file I opened up to work on as files that were small enough did not cause the crash. Not only that but the more I played around the the size of the file that would crash got smaller and smaller. This raises the question is some temporary storage somewhere filling up that shouldn’t?
Anyway, I started uninstalling and reinstalling beginning with 3.6.3 and working backwards trying the older versions I had from previous installs. I didn’t have any luck getting rid of the problem until I installed 3.4.2 where the crashes stopped. God knows why. While this is not a fix it is a band-aid if you are willing to live with an older version and crashes don’t start happening again. Hopefully this will get a better resolution in the near future.
By the way I used REVO Uninstaller (free version) as it also allows you to delete any leftover files and registry entries after the uninstall.
Same with me. Version 3.6.0 was the last that caused no crashes on my system.
Windows 11
Ryzen 5 5600X
Radeon RX6600
64GB Ram
256GB SSD for system.
No other App causes similar problem.
3.6.3 is crashing on exit every time. Windows 10, everything from C drive. On restart it has to discard a lot of undo settings it says. Reporting here because sending error does not work.
hello @here
please try again with 3.6.4 - it fixes another crash on close
1 Like
No more crash.
Thank you !
Can you describe briefly what this one fixes?
Example: Fixes a Windows crash when you export a stereo MP3 of a flute solo on Thursday.
Koz
No idea tbh. It seems the fix just blanketed a bunch of null checks across the project window:
This probably doesn’t address the root cause, but it’s good enough to fix the crash, so…
Thanks. Have tested 3.6.4 out on files/folders in both C Drive and D Drive and had no issues so far upon closure or exiting. Great work. Thanks again.
1 Like
Sorry I didn’t get back to you sooner. I was in the hospital for a couple of days and am still recovering from surgery. A quick check results in no occurrence of exit on close. This is great news. I will let you know if it reappears in the future. Thanks!
This topic was automatically closed after 30 days. New replies are no longer allowed.