14.07.2025, 14:47
Haven't noticed this yet.
Hybrid, by default, starts any process with 'IDLE' priority, so it's always up to the OS to assign resources.
My guess is that, your system is Windows and runs in efficiency mode in which any process without an active window is assumed to need that much cpu resources. So the cpu might be clocking down even if there are still processes running, which could need the power.
(if efficiency cores are available, spawning sub-processes might get sent to those instead of the performance cores)
=> from what I know this nothing caused by Hybrid, or the tools it uses, but by the way you configured your OS.
if you are using Windows, see: https://support.microsoft.com/en-us/wind...9ea2175734
Cu Selur
Hybrid, by default, starts any process with 'IDLE' priority, so it's always up to the OS to assign resources.
My guess is that, your system is Windows and runs in efficiency mode in which any process without an active window is assumed to need that much cpu resources. So the cpu might be clocking down even if there are still processes running, which could need the power.
(if efficiency cores are available, spawning sub-processes might get sent to those instead of the performance cores)
=> from what I know this nothing caused by Hybrid, or the tools it uses, but by the way you configured your OS.
if you are using Windows, see: https://support.microsoft.com/en-us/wind...9ea2175734
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.