I'm curious to understand why starting e.g. Chrome for the first time adds 30 Watts permanently, even after I close Chome.
I see 2 chrome.exe procs using 3.5% GPU each.
When I close chrome, that GPU usage goes away and no other procs except for csrss.exe (uses 0.7%), but the watts go down by only ~3 if anything.
I'd suspect chrome initialization starts up some e.g. system tasks that eat up CPU or GPU even after it is finished, however, I don't see any GPU usage (according to list of procs in ProcessExplorer) and CPU doesn't go up to make up for anything the GPU was previously doing.
I'll have to double check what CPU is before ever starting Chrome after a reboot to see how much CPU overall, goes up, but doesn't come down, after starting and ending Chrome.
If you know how I might avoid a reboot and clean up any mess starting Chrome might have left, I'd be happy to learn it! : )