Unable to send "Problem Report"

I’m new to this forum, but searched and couldn’t find any existing thread on this exact topic. I use Audacity occasionally (but also Reaper, Cubase, Wavelab…). Audacity crashes frequently, so I was interested to see a new Audacity version a few days ago claiming to fix various issues, including ‘crashes’. However, Audacity continues to crash predictably for me (Windows 10, 64 bit…), often when I try to close a project or exit Audacity. When the “Problem Report for Audacity” appears, I try to “Send” but am ALWAYS then told “Failed to send crash report”. I have email installed, an active Internet connection, etc., but is there something I must configure within Audacity to allow sending the error report? I am presently running Audacity 3.6.2, which I think is the latest.

Oh… and I don’t do anything ‘fancy’… i may record, normalize, export, close… record, normalize, export, close… something like that will cause the crash virtually 100% of the time.

Any guidance/advice?

Thanks in advance.

Both the crashes and the failed report sending are known bugs. Muse are working on the crashes, but can’t figure out why the reports don’t send.

Peter

Thank you for the update.

Unfortunately, Audacity 3.6.3 appears to have made the problem worse.

Before, Audacity would crash when I exited. Now, Audacity crashes a few minutes after I start using it.

And I remain unable to send any problem reports.

1 Like

One additional observation… the behavior has changed and now appears to be a bit more intermittent.

On my Windows 10 (64 bit) today, I opened a file, inserted a bit of silence at the beginning and again at the end, normalized and exported the audio, closed the file and repeated with another file… Once, it crashed while using Audacity… other times it crashed only when I exited Audacity.

To quantify further, I just opened/edited/exported 21 files… Audacity crashed during use 8 times.

@fallen_trumpet

See this bug which has been recently re-opened and re-fixed (a long thread to read):

There should be a 3.6.4 bug-fix release out soon for this fix.

Peter

This topic was automatically closed after 30 days. New replies are no longer allowed.