Bugzilla – Bug 1869
Closing Audacity when uncompressed file imported "faster" aliased are used can sometimes cause a crash
Last modified: 2019-08-07 06:54:11 UTC
Issue reported on Windows and confirmed on Linux, so assumed all platforms. The bug does occur for me in debug builds, only release builds. Affects Audacity 2.2.2 and 2.3.0 alpha, so a regression even though not against 2.2.2. With a release build, it occurs for me about one time in 5. See steps to reproduce. Initially set as P4 as no data is lost, but possibly borderline P3.
Promoted to P3. Audacity should not have repeatable crashes.
(In reply to Steve Daulton from comment #0) I cannot reproduce this on 2.2.2 or on 2.3.0 alpha (not debug builds) Testing on W10 laptop Steps 1) set prefs to faster aliased import (not copy in) 2) Imort WAV file 3) Edit bit - amplify 4) Export WAV to new file name 5) top right "X" to close Audacity 6) choose "don't save" => Audacity closes cleanly with no crash repeat many times => no crash
(In reply to Peter Sampson from comment #2) If you process the imported track, then the project will not be using alias files, which appears to be a requirement for the crash. Are you able to reproduce the crash with the stated "Steps To Reproduce"?
(In reply to Steve Daulton from comment #3) >Are you able to reproduce the crash with the stated "Steps To Reproduce"? Ah yes - but only occasionally - maybe on in 7-10 closes - the rest close ok (that is a guestinate not accurate run-rate)
For 2.3.3 On-Demand loading of aliased files is being removed so this bag can no longer occur.
Testing on macOS 10.14.5 Mojave with 2.3.3 Mac alpha jc005 of 01Aug19 As with Windows - this can no longer be tested on Mac as OD has been removed
Closed as WONTFIX for 2.3.3 and onwards - as aliased files can no longer be created in new projects from 2.3.3 onwards. We will continue support for the use of aliased external audio files in 2.3.3 and onwards for projects created in 2.3.2 and earlier which have dependencies on aliased external audio files - so users need to be aware of this. To this end a P3 superbug Bug #2189 has been created with a relevant release note.