Bug 493891 - When CPU usage and lag is high, Spectacle recordings are way shorter than they are meant to be
Summary: When CPU usage and lag is high, Spectacle recordings are way shorter than the...
Status: RESOLVED DUPLICATE of bug 471159
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 23.08.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Noah Davis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-30 21:25 UTC by Ellie
Modified: 2024-10-01 17:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ellie 2024-09-30 21:25:44 UTC
SUMMARY

When CPU usage and lag is high, when pressing stop while a Spectacle recording is going on, it will often be cut off way too short by a significant amount like ten seconds or longer. It seems like the recording somehow needs to "catch up", and when pressing stop it doesn't save until the time when I actually pressed stop but rather only to wherever the internal video creation process has caught up to at that point. This seemingly makes it impossible to actually end a screen recording at a predictable point without neither tons of nothing at the end nor a significant action cut off.

STEPS TO REPRODUCE

1. Cause a lot of CPU and GPU load that is ongoing
2. Start spectacle recording
3. Do some actions on screen, then stop right after the last action

OBSERVED RESULT

The video is laggy, which is expected. The video is also way shorter and cuts off a lot of what you did on screen before pressing stop, which isn't expected.

EXPECTED RESULT

The video isn't cut short even when the system was experiencing lag.

SOFTWARE/OS VERSIONS

Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: postmarketOS Edge based on Alpine 3.21.0_alpha20240923
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.6.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-10-01 17:15:10 UTC

*** This bug has been marked as a duplicate of bug 471159 ***