Memory issues with 6 beta
Memory issues with 6 beta
I am running 6.0 Beta and seem to be having memory issues.
the Host Monitor pc was using 950 megs of memory, when I stopped the host monitor service the memory use dropped instantly to 121 meg.
windows task manager Processes only showed Host Monitor as using 257 meg of memory.
I am also using the RCC 1.50 beta client, That also is using 257 meg of memory and climbs daily if left open.
These memory issues just started after upgrading to 6.00 from 5.82.
StevenE
the Host Monitor pc was using 950 megs of memory, when I stopped the host monitor service the memory use dropped instantly to 121 meg.
windows task manager Processes only showed Host Monitor as using 257 meg of memory.
I am also using the RCC 1.50 beta client, That also is using 257 meg of memory and climbs daily if left open.
These memory issues just started after upgrading to 6.00 from 5.82.
StevenE
StevenE,
Looks similar to what I experienced although my HM 6.01 Beta "only"consumed 541 MB RAM
FWIW after restarting HostMonitor and letting it run for some 20 hours it now uses 240 MB RAM and 230 MB in the pagefile.
I don't know if that's high but I sent you guys at KS-Sosft our .hml file, perhaps you can tell if this memory usage is normal considering the number of tests to be performed.
Kasper :O)
Looks similar to what I experienced although my HM 6.01 Beta "only"consumed 541 MB RAM
FWIW after restarting HostMonitor and letting it run for some 20 hours it now uses 240 MB RAM and 230 MB in the pagefile.
I don't know if that's high but I sent you guys at KS-Sosft our .hml file, perhaps you can tell if this memory usage is normal considering the number of tests to be performed.
Kasper :O)
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Alex,
> do you use RCC on regular basis as well?
Not on a regular basis, no, but as a matter of fact I did use it once last week and again today.
Clue ?
Note: When using RCC I always connect to 127.0.0.1. Hostmon.exe runs in a terminal session and I connect to it from a RCC running in another session on the same terminal server.
Kasper :O)
> do you use RCC on regular basis as well?
Not on a regular basis, no, but as a matter of fact I did use it once last week and again today.
Clue ?
Note: When using RCC I always connect to 127.0.0.1. Hostmon.exe runs in a terminal session and I connect to it from a RCC running in another session on the same terminal server.
Kasper :O)
KS-Soft wrote:Yes we are trying to reproduce this memory leakage. Problem is we cannot reproduce it so far
Kapz, do you use RCC on regular basis as well?
Regards
Alex
The Memory increase for host monitor took days to increase ( more than a week )
The RCC memory increase took a couple of days.
I have RCC 24/7, we have a remote monitoring station in our IT Room.
Steven
We have tested several instances of HostMonitor on Windows 2000, SP, 2003; we have tested HostMonitor using your test lists as well as our testing lists; we have tested HostMonitor itself and HostMonitor with RMA, RCC and Web Service.
And we cannot reproduce memory leakage.
May be there are no leakage?
You know, "Mem Usage" column displayed by Windows Task Manager shows "Memory Set" counter.
Quote from Microsoft
So, if Task Manager's Mem Usage means nothing, we have added "Memory info" counter into HostMonitor itself.
If you install this update www.hostmonitor.biz/download/hm602d.zip, start HostMonitor, enable Info pane (menu View) and select folder item (not test item), you will see "Memory info" line in the Info pane.
Please check how this counter raising (or not raising) on your system.
Regards
Alex
And we cannot reproduce memory leakage.
May be there are no leakage?
You know, "Mem Usage" column displayed by Windows Task Manager shows "Memory Set" counter.
Quote from Microsoft
This means the more memory you have installed on your system the higher "Mem Usage" value you may see. Hovewer it does not mean HostMonitor uses this memory.Working Set is the current number of bytes in the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before they leave main memory.
So, if Task Manager's Mem Usage means nothing, we have added "Memory info" counter into HostMonitor itself.
If you install this update www.hostmonitor.biz/download/hm602d.zip, start HostMonitor, enable Info pane (menu View) and select folder item (not test item), you will see "Memory info" line in the Info pane.
Please check how this counter raising (or not raising) on your system.
Regards
Alex
I could agree with that, except
When the pc running host monitor is using most or more of the memory.
The second I stop the Host Monitor service all the memory is released.
And this has never happened when running 5.82.
Not when I stop the webservice, the server service or any other service.
The memory is only released when I stop the host monitor service.
The Host Monitor pc is now using 500 meg of memory a jump of 300+ meg more than yesterday. ( I have been keeping track ).
This will keep increasing until the pc has almost no resources left and then stop working properly.
I will send you what info you have alread requested.
Steven
When the pc running host monitor is using most or more of the memory.
The second I stop the Host Monitor service all the memory is released.
And this has never happened when running 5.82.
Not when I stop the webservice, the server service or any other service.
The memory is only released when I stop the host monitor service.
The Host Monitor pc is now using 500 meg of memory a jump of 300+ meg more than yesterday. ( I have been keeping track ).
This will keep increasing until the pc has almost no resources left and then stop working properly.
I will send you what info you have alread requested.
Steven
Alex,
> If you install this update www.hostmonitor.biz/download/hm602d.zip
Done.
> But looks like we have reproduced problem with RCC...
> Could you do not use RCC for several days and watch memory?
Sure. Would be nice to be able to monitor the "correct" value that HostMonitor supplies through the Info pane though.
Through detailed logging I might be able to track down what exactly happened/what exactly I was doing when HM's memory use suddenly went nuts.
Any way to do this ?
Kasper :O)
> If you install this update www.hostmonitor.biz/download/hm602d.zip
Done.
> But looks like we have reproduced problem with RCC...
> Could you do not use RCC for several days and watch memory?
Sure. Would be nice to be able to monitor the "correct" value that HostMonitor supplies through the Info pane though.
Through detailed logging I might be able to track down what exactly happened/what exactly I was doing when HM's memory use suddenly went nuts.
Any way to do this ?
Kasper :O)