[Bug] Memory Leak in UsageMonitor... or Windows PerfMon?
Posted: May 24th, 2018, 11:39 pm
Hello!
I hesitate to post this since 99% of the time these sorts of posts are baseless, but there seems to be a memory leak someplace. Unfortunately, I don't have a good way to point a developer at a particular point in the code, but I'm happy to help in any way that I can.
Typically when I run Rainmeter with my usual set of skins active, Rainmeter consumes roughly 35MB of RAM, and this remains very steady. However, when I add a skin that has many instances of UsageMonitor measures (a "top process" skin), the Rainmeter process slowly consumes memory. After about 8 hours, memory is about 70MB and slowly increasing. I have not had time to let this run for a very long time under different conditions, but at one point I did let Rainmeter run this skin continuously for 3 days; at that point RM was using several hundred megabytes of RAM and -- unfortunately at some point while I was not looking -- RM seems to have crashed or something, because it was completely gone (no error message). So I was not able to see any message or attach a debugger. I have not had time to try duplicating this, but the memory issue is easily replicated.
I know this info is probably of little help. In case it matters, this is happening on multiple machines, including a "clean" VirtualBox VM with nothing on it except Rainmeter.
4.2.0 beta r3064 64-bit (May 13 2018) - English (1033)
Windows 10 Pro 1803 64-bit (build 17134) - English (1033)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\xxx\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\xxx\AppData\Roaming\Rainmeter\
IniFile: C:\Users\xxx\AppData\Roaming\Rainmeter\Rainmeter.ini
Finally, if it is of any value, I've attached the skin demonstrating the issue. I don't think this skin is doing anything too abnormal, no extra plugins or etc., but perhaps I'm doing something that is causing an issue.
I hesitate to post this since 99% of the time these sorts of posts are baseless, but there seems to be a memory leak someplace. Unfortunately, I don't have a good way to point a developer at a particular point in the code, but I'm happy to help in any way that I can.
Typically when I run Rainmeter with my usual set of skins active, Rainmeter consumes roughly 35MB of RAM, and this remains very steady. However, when I add a skin that has many instances of UsageMonitor measures (a "top process" skin), the Rainmeter process slowly consumes memory. After about 8 hours, memory is about 70MB and slowly increasing. I have not had time to let this run for a very long time under different conditions, but at one point I did let Rainmeter run this skin continuously for 3 days; at that point RM was using several hundred megabytes of RAM and -- unfortunately at some point while I was not looking -- RM seems to have crashed or something, because it was completely gone (no error message). So I was not able to see any message or attach a debugger. I have not had time to try duplicating this, but the memory issue is easily replicated.
I know this info is probably of little help. In case it matters, this is happening on multiple machines, including a "clean" VirtualBox VM with nothing on it except Rainmeter.
4.2.0 beta r3064 64-bit (May 13 2018) - English (1033)
Windows 10 Pro 1803 64-bit (build 17134) - English (1033)
Path: C:\Program Files\Rainmeter\
SkinPath: C:\Users\xxx\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\xxx\AppData\Roaming\Rainmeter\
IniFile: C:\Users\xxx\AppData\Roaming\Rainmeter\Rainmeter.ini
Finally, if it is of any value, I've attached the skin demonstrating the issue. I don't think this skin is doing anything too abnormal, no extra plugins or etc., but perhaps I'm doing something that is causing an issue.