https://bugs.kde.org/show_bug.cgi?id=475894
--- Comment #5 from Noah Davis <noaha...@gmail.com> --- 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. -- You are receiving this mail because: You are watching all bug changes.
