Bugzilla – Bug 2259
Windows: wxWidgets 3.1.1 debug failure message appears on Timer Record start recording
Last modified: 2020-03-11 13:50:06 UTC
Last night using the latest Windows 2.4.0 alpha audacity-2.4.0-alpha-370-45c6a70d17febbb8de691665ce857cd4bfd9dd78 I set a two hour Timer Recording to run from Midnight to 2am - the Timer Record setup proceeded smoothly and the waiting to start dialog was properly displayed On returning to this the following morning I saw that the recording had not started at the appointed time - rather a wxWidgets debug message was being displayed (halting the Timed recording). Dismissing the wxWidgets debug error message resulted in the Timer Recording starting - but hours outside the prescribed time window for the recording (I did not try let it run the full two hours to see if it would stop then or run on longer). This is a moonphase error, it is the first time I have encountered it (and I run such a TR, boldly in the interests of QA, on alphas weekly). I cannot reproduce this this morning with test Timer Recordings It has two close cousins Bug #2074 and Bug #2075 - they are rated as P3 as dismissing them enables Audacity to proceed. I have made this one P2 (marginal P1) as it causes the irrevocable loss of data, in last night's case a radio show that will not be rebroadcast/repeated. I am tempted to mark this as "regression" as I have never encountered this before. ---------------------------------------- It begs a fundamental question: just why are we having debug messages in production software ? Note that this was *not* a debug build of alpha Audacity.
Created attachment 883 [details] WXwidgets debug message on starting recording in Timer Record WXwidgets debug message on starting recording in Timer Record
Prior to setting up my weekly midnight to 2am Timer Record last night I teste first with the latest 2.4.0 alpha: audacity-2.4.0-alpha-371-9dab0a2fee70826c63db43a8afb48c5897c5c4d8 Again this generated the wxWidgets alert message that suspended the start of the timed recording waiting for user acknowledgement. Accordingly, in the interests of data safety, I reverted to using 2.3.3 - this worked unattended with no problem.
Elevating this to P1 as it makes Timer Record on 2.4.0 too dangerous to use with the risk of irrecoverable data loss
Peter, I'm unable to recreate it and I believe this was fixed in commit: https://github.com/audacity/audacity/commit/036efda65ee793402408503703d8239d7c361c99 Can you give 'er a try again and see what you think?
(In reply to Leland Lucius from comment #4) Testing on W10 with latest alpha Audacity 2.4.0 windows-2019_2803bc3 And thus far, with many attempts, I've not been able to get it to fail (it is Moonphase anyway though). I have updated this thread but will leave it open for now and in my test workbench - so I will continue to test it for a while. I will revert to using the alpha builds for my weekly overnight 2-hour production Timer Recordings
(In reply to Peter Sampson from comment #3) I have tested this daily on W10 with various alphas since Leland's comment #3 - sometimes several times a day. Plus I have used this "in anger" several times to record my unattended Monday night midnight to 2am webshow from Dublin City FM. I have not encountered the wxWidgets warning = accordingly I am going to close this bug as FIXED - we can reopen or relog later if ever necessary.
