Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



First Last Prev Next    This bug is not in your last search results.
Bug 2617 - Audacity not responding after switching to Envelope tool
Audacity not responding after switching to Envelope tool
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Application Core
3.0.0
All Windows and macOS
: P2 RepeatableAll
Assigned To: Default Assignee for New Bugs
https://forum.audacityteam.org/viewto...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2020-12-31 10:23 UTC by Steve Daulton
Modified: 2021-01-03 05:39 UTC (History)
7 users (show)

See Also:
Steps To Reproduce:
1. Launch Audacity 2. Launch "Task manager" expanded and arrange the windows so that both Audacity and Task Manager are visible 3. Generate a tone 4. Add some envelope points 5. Zoom out 6. Make a selection in the empty part of the track 7. Generate a Chirp 8. Move the mouse pointer over the first audio clip (with envelope points) 9. Press "F2" 10. Observe: Envelope Icon is not selected in the Tools toolbar Observe: Envelope points do not appear Observe: Task Manager shows Audacity power usage is "Very high" Observe: Task manager indicates 100% of one CPU core Observe: After a few moments, the "busy" icon appears and Audacity shows "Not responding" in the title bar 11. The "busy" state continues until the mouse is moved away from the audio track. If the problem does not occur straight away, after step 9: 12) Press "F1" 13) Make a new selection in the second audio clip 14) Move the pointer over the first audio clip 15) Press "F2" 16) Observe symptoms in Steps 10 and 11
Release Note:
Group: Tools shortcuts Audacity may not respond when you use the F2 shortcut to switch to envelope tool when the cursor is over the waveform or track
First Git SHA:
Group: ---
Workaround:
Move your cursor away from the track
Closed: 2021-01-03 00:00:00
stevethefiddle: Regression+
petersampsonaudacity: Test‑OK‑Win+
petersampsonaudacity: Test‑OK‑Mac+
stevethefiddle: Test‑OK‑Lin+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Daulton 2020-12-31 10:23:20 UTC 
On pressing "F2" to select the Envelope tool, Audacity may display "Not responding" with 100% CPU usage on one CPU core.

Observed in Audacity 2.4.2 and 3.0.0.

Believed to be a regression, though I've not tested earlier than 2.4.2.

Does not occur on Linux.
Comment 1 Peter Sampson 2020-12-31 11:02:58 UTC 
Testing on W10 with Audacity 3.0.0 f7c0ba8

This does not happen for me:

a) at Step 10 the envelope points apperta properly

b) Task manager shows Audacity power usage shows "very low"

c) Task manager shows 6% CPU usage for Audacity, dropping to 0.5%

d) The Windows busy icon does not appear

e) Audacity remains responsive


WORKSFORME
Comment 2 Peter Sampson 2020-12-31 11:13:13 UTC 
But testing on 2.4.2 shows this fails for me as Steve says on W10
Comment 3 Steve Daulton 2020-12-31 12:41:38 UTC 
It is reproducible for me with both the 32-bit and 64-bit builds of f7c0ba8, though it happens most times, not every time.

If the problem does not occur straight away, after step 9:

i) Press "F1"
ii) Make a new selection in the second audio clip
iii) Move the pointer over the first audio clip
iv) Press "F2"
Comment 4 Peter Sampson 2021-01-01 06:41:41 UTC 
Testing on W10 with Audacity 3.0.0 f7c0ba8

Now with Steve's additional steps I can reproduce this issue on W10 - but only on the second pass - Step 9 still works fine consistently - it only fails (consistently) at Step 15.

Curiously it also fails if at Step 14 you move the cursor to the gray empty track space - but not if you omit step 14 and leave the pointer over the Chirp.
Comment 5 Peter Sampson 2021-01-01 06:57:18 UTC 
Testing on W10 appears to show that this is a regression on 2.3.2
Comment 6 Peter Sampson 2021-01-01 07:39:51 UTC 
Testing on mac OS 11.1 Big Sur with 3.0.0 4cb9bb 9Dec20

I observe the same faulty symptoms at Steps 9-10 and 15-16,  accordingly I changed this to all platforms



I cannot test on latest alpha as the latest alpha build crashes on launch - P1 Bug #2165
Comment 7 Steve Daulton 2021-01-01 07:53:37 UTC 
I've still not been able to reproduce this issue on Linux, so marked "Windows and macOS".
Comment 9 Peter Sampson 2021-01-01 10:35:38 UTC 
(In reply to James Crook from comment #8)
Testing on W10 with Audacity 3.0.0 7143df2

This now appears to be fixed - Ok at Step 9 and at extended step 15
Comment 10 Steve Daulton 2021-01-01 11:53:38 UTC 
Still looks OK on Linux. I've not found any unwanted side effects.
Comment 11 Peter Sampson 2021-01-03 05:39:32 UTC 
Testing on macOS 11.1 Big Sur with Audacity 3.0.0 f60e19737

Thsi works fine in Mac as well.
First Last Prev Next    This bug is not in your last search results.