Audacity Forum

This should be the latest debug report.

I recently installed Java runtime on my PC. Should I not have done that?

I don't think that makes any difference one way or the other, I was much more concerned with the reference to Oracle.

Are all these drives internal?

You may have turned over a rock. I've never used Control/Command-W. Does Audacity crash the instant you press those keys?

Does it stay up if you click File > Save Project? Simple mouse with no keyboard shortcuts?

Do these tests with the desktop, not with one of the pre-defined directory systems on one of the drives.

See if you can open this simple MP3 file I made. It's mono noise for a minute.

Koz

I split the diagnosis there. Nobody wrote you can't have more than one problem.

Koz

Hello Koz. We have some progress/change.
1) I saved/"open with" your noise file from IE and it opened fine.
2) I created a desktop shortcut for the file, selected "open with audacity" and that worked fine.
3) With the file loaded in Audacity either way, I use the ctrl+w keystroke, get the "do you want to save changes to this file?" dialog box, choose "no" and audacity crashes.

I am a blind user so can't try your mouse-only suggestions. I can only access/navigate via keystrokes.

An interesting thing. I can't open/import files within Audacity without it crashing. However, once I have managed to load a file into Audacity (from desktop/fileexplorer) I am able to import a second file into the session from within Audacity.

Hopeless1 wrote:Here's the latest debug report.

Both your crash reports from Audacity say in audacity.xml that you are on "Windows 8 (build 9200), 64-bit edition" although you claim to be using Windows 10.

Hit the Windows button and type "Winver" (without quotes) then hit ENTER on your keyboard. What does that say for version and OS build?


Gale

Hopeless1 wrote:I recently installed Java runtime on my PC. Should I not have done that?

Java is a severe security threat to your computer because it has unpatched holes that can be exploited by malicious applications. Only use Java if you have legitimate applications that actually use it.

Hopeless1 wrote:With the file loaded in Audacity either way, I use the ctrl+w keystroke, get the "do you want to save changes to this file?" dialog box, choose "no" and audacity crashes.

I am a blind user so can't try your mouse-only suggestions. I can only access/navigate via keystrokes.

Wrong list. The Forum cannot not specialise in helping blind users. The list you want to give you proper support is Audacity4Blind: http://wiki.audacityteam.org/wiki/Audac ... users#docs.

If you are actually using the Windows 10 Creators update (version 1703, build number 10.0.15063 <anything>) with JAWS screen reader, then the crashes you refer to are known about and now fixed in our alpha development source code. Try it in the latest 2.2.0-alpha development build at the top of http://gaclrecords.org.uk/win-nightly/. Alphas are not release builds. Back up your work regularly by exporting as WAV if you use alpha builds.


Gale

Thanks Gale. In response to your points:

I raised my issue here because my problem is with basic software functionality and not about using the app as a blind person.
I am running windows 10 and update daily (see screenshot for version/build). I had previously run Audacity without event on my old PC (updated from 7 to 10) with JAWS.
Thank you for that link. I shall try it.

Hopeless1 wrote:Thanks Gale. In response to your points:

I raised my issue here because my problem is with basic software functionality and not about using the app as a blind person.

My answer is the same. The helpers on this Forum, except one, do not use screen reader software. We do not support blind users on Audacity Forum. Please observe the length of this topic already, because you wrote to the incorrect board. Audacity4Blind would have given you the correct answer to the problem straight away.

Hopeless1 wrote:I am running windows 10 and update daily (see screenshot for version/build). I had previously run Audacity without event on my old PC (updated from 7 to 10) with JAWS.

As I said, the crashes are with Windows Creators Update and the JAWS reader. Previous versions of Windows are not affected. Other screen readers are not affected even with Creators Update. Those using no screen reader will also not see these crashes.


Gale