2.2.1 Doesn't Crash Only When Run as Administrator

Hello All,

We are currently facing an issue where Audacity 2.2.1 will crash when a user imports a sound file or after a recording is done.

I was testing on a machine where I was recording audio, and during the recording, it seemed to just stop. Here is a screenshot: https://i.imgur.com/Q8eN614.png

Pressing the play button does absolutely nothing.

Trying to close the application prompts me with the debug report. I tried to open the dump file, but it looks like gibberish and I don’t know what to use to read it.

This happens on all ~40 machines we have. Here are their specs:

Dell OptiPlex 7040
Windows 7 64-bit SP1 Build 7601

I also attached the dump file if it helps.

Don’t use Audacity 2.2.1. It has a serious bug (see: https://forum.audacityteam.org/t/important-bug-fix/48358/1)
Audacity 2.2.2 fixes this bug, and is available here: Audacity ® | Downloads

Are these computers on a network?

Okay, I will try that on a couple machines to verify.

Yes, and they are technically on three different GPO groups, IIRC.

We have a very complex, but manageable network at our University. :unamused:

To record with Audacity it is essential that Audacity has read/write access to:

  1. Its configuration files
  2. A temp directory for reading/writing audio data.

As Audacity is required to access (read/write) time critical data (audio does not wait), both of these locations, and the Audacity application, should be on local storage (an internal hard drive or SSD). Attempting to record to a remote (network) drive will fail because data has to be written and read in real time, and there’s a lot of data.

Has Audacity been installed locally (on the local computer’s hard drive), and do the normal (non-admin) accounts have read / write access to Audacity’s temp directory, and do normal accounts have read/write account settings for “Users//AppData/Roaming/audacity/”? In other words, is Audacity correctly installed to run on the local machine?