https://bugs.kde.org/show_bug.cgi?id=475894
--- Comment #6 from sombriks <sombr...@gmail.com> --- (In reply to Noah Davis from comment #5) > Just letting people know, I'm currently unable to reproduce this bug. My > assumption right now is that it's similar to the problem I get when using > the wrong encoder settings with a stream, which is that the RAM usage grows > rapidly until OOMing if it can't process the incoming frames quickly enough. > > I think that this issue should be more commonly encountered on systems with > weak CPUs, but that doesn't explain why Viniciusdaros's PC had the problem. > I have an AMD Ryzen 7 4800H with Radeon Graphics and 30.8 GiB of RAM. > Viniciusdaros has much lower RAM than me, but their CPU is not vastly > different in performance > (https://www.notebookcheck.net/R7-5700U-vs-R7-4800H_12978_11677.247596.0. > html). Based on my observations under normal circumstances, Spectacle's RAM > usage should be 200-300 while GPU encoding and 2x that while CPU encoding > (depends on the encoder). Under normal circumstances, 6.6 GiB of RAM should > be enough to record with Spectacle without OOMing unless the system is > already close to running out of RAM. I got the same issue on same hardware on openSUSE Tumbleweed KDE and Fedora 39 KDE, but i recently formatted it again, Fedora 39 with GNOME and default GNOME's recording tool does not suffer of any memory leak. it just keeps recording and recording my screen. The system is a ThinkPad T14 Gen 2a with 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics and 48GB of RAM I am unable to format at the moment, but let me know if virtual machines are good to try to reproduce the issue, and if there is any specific version or parameter to pass so we can get more detaile info. -- You are receiving this mail because: You are watching all bug changes.
