Iridium-IO
commented
4 months ago Too risky to be honest, I wasn't comfortable with the idle detector in the first place and your memory leak issue is good enough reason for me not to try to get creative with other forms of usage detection.
Even Microsoft doesn't seem to know how to do idle detection properly (windows defender running at the worst times, indexing service deciding the middle of a game is the best time to run), the whole thing is cursed.
I have a very powerful CPU, so it's not an issue for me to even play games in the background during compression. Not to mention, when I'm on discord or watching youtube or netflix or the like, I doubt background compression would create any significant amount of lag.
Perhaps maybe a CPU usage threshold or disk usage threshold should be the primary influence on the trigger background compression as opposed to input?