Hello everyone!
I'm new here, so please be nice to me!
I've discovered a somewhat weird behavior of my currently used HWInfo64 v4.14-1880...
First of all, I'm working as an IT Customer Supporter, hence my work PC is running more or less 24/7! BTW, I'm local admin on my box, so we can exclude permission issues or like that...
After some days (in my case 13, almost 2 weeks) of permanently running of HWInfo64 after the last reboot I got today a Windows 7 warning message, that my box was running low on memory! Opening the Windows Task Manager showed me the culprit very fast: HWInfo64 was consuming almost the half (3.5GB) of my available 8GB RAM! (and yes, as shown in the screenshot I'm very aware there are a lot of other open programs also consuming memory, especially the RAM hog Chrome...)
I did some screenshots and also made a System-Report with HWInfo64 to proof my above statements! (see Attachments)
If this behavior was already reported to this forum, then my apologies, but I didn't find any clues for my circumstances! BTW, this isn't my first case with HWInfo64, the situation also happened with former (64bit) versions of it so far...
In case of questions feel free to ask me any time!
Yours
Sparksman
I'm new here, so please be nice to me!
I've discovered a somewhat weird behavior of my currently used HWInfo64 v4.14-1880...
First of all, I'm working as an IT Customer Supporter, hence my work PC is running more or less 24/7! BTW, I'm local admin on my box, so we can exclude permission issues or like that...
After some days (in my case 13, almost 2 weeks) of permanently running of HWInfo64 after the last reboot I got today a Windows 7 warning message, that my box was running low on memory! Opening the Windows Task Manager showed me the culprit very fast: HWInfo64 was consuming almost the half (3.5GB) of my available 8GB RAM! (and yes, as shown in the screenshot I'm very aware there are a lot of other open programs also consuming memory, especially the RAM hog Chrome...)
I did some screenshots and also made a System-Report with HWInfo64 to proof my above statements! (see Attachments)
If this behavior was already reported to this forum, then my apologies, but I didn't find any clues for my circumstances! BTW, this isn't my first case with HWInfo64, the situation also happened with former (64bit) versions of it so far...
In case of questions feel free to ask me any time!
Yours
Sparksman