Yet another version of Audacity, yet another one that doesn’t address the above issue. It’s been referenced several times over the years, never with any satisfactory response. Time after time I’ve tried to send the Problem Report, which always fails. Unfortunately it’s far too big to quote here.
We have all manner of fripperies being added with each new version, icing on the cake, but basic issues like this persist. Can we have an official response?
Not an official response, just my 2c.
I understand your frustration with bugs, but “Exception Access Violation Read” is not one specific bug, it is a symptom. It means that something tried to access an invalid memory location, but on its own it gives no clue as to what went wrong or why.
Looking back through the forum, there’s a bug here which produced this error: Nyquist plug in installer keeps crashing on version 3.4.1
and in this case the bug was fixed in 3.4.2
Another one here that was apparently fixed in 3.4.2: I can't open old audacity projects since new update - #19 by jademan
Without more context, the error “EXCEPTION_ACCESS_VIOLATION_READ” does not tell us much more than “something went wrong”.
For a developer to fix a bug, they need to know how to reproduce the bug. If you are getting crashes, try to isolate exact steps that will allow others to reproduce the problem - if you can do that, then that gives the developers something specific to investigate (and hopefully fix).
Thanks Steve, I’m doing nothing more than I’ve always done, stringing together and mixing .mp3 files and voice clips recorded with Audacity. It seems to be worse in 3.6.0 so I’ve regressed to 3.5.1, where the crashes were occasional, and I’ll see what happens.
I suspect the lack of action is because of the lack of crash reports, which fail every time I try to send. Reading the forums it seems I’m not alone. As an ex-mainframe developer I’m not unsympathetic, knowing how difficult it is to fix a bug without the evidence. A good start would be to fix the mechanism for sending crash reports.
Hi same with me… crashes on exit for last version and the new 3.6.0 just released… I have a new rig so surprised. I removed and went back to 3.4.2 and works as expected.
Possible clue… I read in a previous bug report with same issue that the poster noticed it said his chip was AMD but he has INTEL, same with me…
Mine’s Intel too, not the fastest but sufficient for my needs. I doubt it’s a processor issue but I’ll stand corrected if wrong.
Intel(R) Core™ i5-7400 CPU @ 3.00GHz 3.00 GHz
Regression to v3.5.1 didn’t help, attached is the error report Audacity won’t let me send.
Error Report.txt (111.5 KB)
The crash report you posted says:
Operating system: Windows NT
10.0.19045 4651
CPU: amd64
family 6 model 158 stepping 9
4 CPUs
I noticed that. The first is from Settings: System: About - the crash report is as copied. It’s definitely not an AMD CPU. Answers on a postcard to… 
This topic was automatically closed after 30 days. New replies are no longer allowed.