Memory Leak in ModBors Monitoring Service

Alright, here we go again…
I've created another version to try and cleanup that memory from Open- and Libre Hardware. You can find it here.

Also if you just want to test this quickly, instead of replacing the service, you can also:

1. close MoBro
2. stop the ‘ModBros Monitoring Service’ under services
3. right click the newly downloaded .exe and ‘Run as administrator’
4. a black console window should appear - don't close it
5. check ‘http://localhost:42001/version’ in a browser, it should return version 1.0.14
6. start MoBro again (decline if there's a pop-up asking to restart the service)

As long as you don't close the console window, the data will be pulled from this service

almost a straight climb within 10 min for me.

@Seraksab This one is working for me.  Uptime for 2 hours and hovering around 75mb for the main process

Sadly not for me. ~2 hrs
 

After another hour it looks like the memory usage is refreshed. 

 

EDIT: Actually, the service stopped randomly and was prompted to restart.

The same for me, the service was blocked after about 3 hours...

Ok, let's see..
So I've apparently managed to fix the memory leak for some of you, but not all. which I don't really understand how that's possible..
And at the same time I introduced a new bug causing the whole service to crash after a while

Well at least those are different results than before, so I guess I'll call that progress xD

I'll do a bit of testing to see if I can at least reproduce and fix that new crash on my end and will let you know once I have a new version ready.
Thanks for helping out to all of you!

i have noticed the same issue, been running for about 30 mins and already using 257 MB ram. 

Old computer, FX8350, gtx 1080, 32GB ram

@Mpgrimes did you try the standalone versions of OpenHardwareMonitor and LibreHardwareMonitor to see if it's these two for you as well? 

Alright, I gave it another try. New version is here

I could reproduce the crashing and stopping that some of you experienced with the previous version. This should be fixed now.
At least I had this running on my machine for multiple hours now with no issue.

The memory should hopefully be cleared every 10 minutes.

To make sure you're actually running the correct version you can again check ‘http://localhost:42001/version’ in a browser, it should return version 1.0.15 for this

1 hour in. I'll keep an eye on it. 
 

Similar experience after one hour

Yes I did, thx for the suggestion. 

yo, MrSpoon. Is the memory leak climbing higher than 150MB? Just curious as I stopped running Mobro until this is fixed. I'm using my custom Sensory Panel through Aida64 until this is resolved. I still support this project as a Patreon and I love the fact that this runs off my pi4b. You've been testing since the beginning of this thread and I trust the results your getting. If it is staying below 150MB I'll switch back.

~3hrs in

 not sure if this is important but i am on the original version still where i first noticed the memory leak, now of course the memory leak is still there but this version also appears to have multiple copies of the service running

 

Stopped service and replaced the exe, now running with updated.  Tried the browser link to verify version but it still shows 1.0.12, flushed browser cache also.

Thanks i'm gonna try it also! Starting right now :)

after ~12 hrs. At least the service is still  running. 

My memory usage gets above 5GB on the regular. I do use a combination of open-hardware and Hwinfo.   @Seraksab if your team would like. I would be willing to let you remote in and look at the service while it's doing. this. it sounds like one of those oily pig kinds of problems.