I don't think I changed many (if any) settings, I use it to feed sensor readings into Rainmeter skins.
If I reset preferences will that not mess up the HWiNFOSensorId, HWiNFOSensorInstance, HWiNFOEntryId values? I read a lot of them in the skins and it would be not fun having to change them. Otherwise I can reset the preferences and report the mem usage tomorrow.
I reset preferences yesterday around midnight, only changed the minimize at startup options to my liking and this morning the process mem usage is close to 500Mb. I noticed there's new beta available, think it would be worth trying that ?
Hi, beta is the same, ie mem usage growth ~500M in half a day. Your question about specs made me realize I only noticed this leak around after I upgraded my pc about month ago, so maybe related to new hw?
I replaced mobo/cpu/gpu:
Msi Z490 Gaming Plus mobo
Intel i7-10700K cpu
Msi RTX 3090 gpu
Drivers are always latest stable, I'm a bit OCD about that.
I have analyzed the data, but don't see anything suspicious except Hyper-V being active. Can you first try to disable Hyper-V if that will make a change?
If not, please try to disable sensors one by one (hit Del key over the sensor heading) and watch if disabling one of them will stop the memory leaking. I'd start with the GPU or disk sensors.
I'm enabling the sensors bit by bit so far I've got all input voltage and temps selected and the leak is not there. This will probably take a while, but I'll keep enabling the sensors every half a day or so and report back.
Well this was faster than I thought, but I got the culprit 100% reproducible and recorded it. It's GPU Power. In the vid notice how the memory rises every ~2 sec when it is enabled. I then enable all the other sensors but leave GPU Power off and the memory usage doesn't move. Then after enabling GPU Power the memory rises again constantly. Hope that helps. For now I left the sensor disabled.