Bug 502852

Summary:	Spectacle crashes and causes high CPU/RAM usage during screen recording
Product:	[Applications] Spectacle	Reporter:	Zakaria Farhati <zakariafarhati18>
Component:	General	Assignee:	Noah Davis <noahadvs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	kde, nate
Priority:	NOR
Version First Reported In:	6.3.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Zakaria Farhati 2025-04-15 17:34:06 UTC

Summary: Spectacle crashes and causes high CPU/RAM usage during screen recording

Description:
When I start a screen recording using Spectacle, the application either immediately freezes or crashes. If I manage to stop the recording, the CPU and RAM usage spikes drastically, and my PC fans ramp up loudly, indicating a system resource overload. The performance impact continues until I manually kill the process.

Steps to reproduce:
Open Spectacle.
Click the "Record Screen" option.
Start recording.
Observe freezing/crashing behavior.
Stop the recording (if possible).
Observe CPU and RAM usage increase sharply.

Expected behavior:
Spectacle should record the screen smoothly and stop recording cleanly without consuming excessive system resources.

Actual behavior:
App freezes or crashes upon starting recording.
After stopping, CPU and RAM usage spike heavily.
Fans get loud, system becomes sluggish.

SOFTWARE/OS VERSIONS:

Operating System: openSUSE Tumbleweed-Slowroll 20250402
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-1-default (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

Comment 1 Nate Graham 2025-04-16 16:07:59 UTC

What video format are you using? VP9 or MP4? Does the issue change or go away of you use a different video format?

Comment 2 Bug Janitor Service 2025-05-01 03:47:42 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2025-05-16 03:47:04 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.