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 1952 - Windows: Timer Record - debug failure msg
Windows: Timer Record - debug failure msg
Status: RESOLVED QUICKFIXED
Product: Audacity
Classification: Unclassified
Component: User Interface
2.3.0
PC Other
: P4 RepeatableAll
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2018-08-29 08:48 UTC by Peter Sampson
Modified: 2018-08-30 05:03 UTC (History)
5 users (show)

See Also:
Steps To Reproduce:
1) Timer Record 2) advance start date year to 2118 or 2500 3) Click OK 4) Observe: Timer record pops up the debug failure message (see attachment) 5) you cannot use the "OK" button to continue as it keeps on re-showing the debug failure message 6) Clicking the "Stop" button aborts Audacity
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed:
petersampsonaudacity: Test‑OK‑Win+

Attachments
debug failure message in Timer Record (29.83 KB, image/png)
2018-08-29 08:48 UTC, Peter Sampson 		Details
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 Peter Sampson 2018-08-29 08:48:41 UTC 
Created attachment 777 [details]
debug failure message in Timer Record

Using the Time record with a date long in the future causes a debug failure message to appear.

I tested with year 2500 and 2118 and both give the error - but 2030 is ok so I think P4 may be sufficient for this.

Such messages should not show in release builds

W may want to raise the priority as you cannot use the "OK" button to continue as it keeps on re-showing the debug failure message - and Clicking the "Stop" button aborts Audacity (which is effectively a crash)



Does not happen on Mac (even with year = 2500) with latest alpha build from Steve:  audacity-macos-2.3.0-85f13b.dmg - 28.82 MB | version: 2.3.0 alpha 85f13b

so assume Windows only for now
Comment 1 Peter Sampson 2018-08-29 10:14:18 UTC 
>We may want to raise the priority as you cannot use the "OK" button to 
>continue as it keeps on re-showing the debug failure message - and 
>clicking the "Stop" button aborts Audacity (which is effectively a crash)

But there will be no data loss - as Timer Record requires only the current project to be open AND requires the current project to be Saved before Timer Record setup is initiated.
Comment 3 Peter Sampson 2018-08-30 05:03:23 UTC 
Testing on W10 with audacity-2.3.0-alpha-108-d050afb6583a508353fc7c5de81ee8a982b3762f

I now get no debug failure message
First Last Prev Next    This bug is not in your last search results.