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).