Bugzilla – Bug 1603
(mac) AUNBandEQ crashes Audacity
Last modified: 2018-08-20 11:51:52 UTC
Regression on 2.1.1.
Created attachment 722 [details] stack trace
I did not succeed in reproduing this on macOS 10.11.6, running the 2.1.3 release, or running builds of my own, either debug or release, at Audacity-2.1.3 The supplied strack trace looks like an overflow because resizing somehow makes an infinite recursion.
This is a guess at a fix from the stack trace data. My mac (at 10.11.6) did not reproduce the problem, and I don't know what system details might account for that. Someone else should clearly compare before and after this commit to verify the fix. https://github.com/audacity/audacity/commit/f1aa9161f05278065ec39d94503c9f290eca43f1
(In reply to Paul L from comment #3) Testing on macOS Sierra 10.12.5 with Cliff's nightly build of 22Jul17 I enanabled the AUNBandEQ effect and then opened it to apply to some audio. No spinning beachball-of-death - but instead now the effect dialog appears - and looks to be working. I will therefore close this bug as resolved/quickfixed
(In reply to Peter Sampson from comment #4) Not so fast: as I said, I could not get the crash on my system without the fix, but guessed at a fix for Gale's from the stack trace he supplied. To close this honestly requires a before-and-after demonstration of problem and problem solved.
(In reply to Paul L from comment #5) Well I get the spinning beachball-of-death (and Audacity crash) consistently on 2.1.2 on my Mac when trying to use AUNBandEQ - but with Cliff's 22 July build I consistently do not. You may have problems getting Gale to do a re-test on his Mac kit as he is not able to perform testing right now (as he stated elsewhere)
2.1.2? I'd like to hear that you got the crash in 2.1.3, to be more confident it's the same crash.
(In reply to Paul L from comment #7) I still get the spinnining beachball-of-death when trying to use AUNBandEQ on 2.1.3
(In reply to Peter Sampson from comment #8) In that case, I agree that this merits closing. For the record, record in these comments what your OS version is. A difference might explain why I could not reproduce the crash.
For the record I stated in Comment #4 what my OS is