-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force ending test in overrun window leaks a buffer restart timer #350
Comments
|
So we're aware that the video is undersized but we just do the best we can with what we have at that point and accept the reduced video duration. That's not much good if we want a 270s video but end up with 10s x) |
See Recorder._bufferRestartIntervalID which I think is what is leaking on updating config. On updating config we call .reconfigure() on the recorder class, we don't re-create it for dull reasons. |
Hm less clear that this is a reconfigure() issue after another look at logs. At 19:33:54 where the first double restart happens, tracking back 5 mins to 19:28:54 looks like there was a test button going on there. The reconfigure a bit earlier doesn't seem to line up with the problem and looks to have worked fine. |
I reckon the force stop caused this |
Probably a bug where the user force ended the test recording during the overrun window. |
So the overrun ends and restarts the recording, and the force end also restarts the recording. So I guess that's how we end up with two buffer restart intervals. A fix is probably to just check we don't have a bufferRestartIntervalID variable before we call setInterval() in Recorder.startBuffer() |
Causes games to be cut in half.
WarcraftRecorder-2023-03-30.log
The text was updated successfully, but these errors were encountered: