Thanks for report, We will investigate it.

Same issue on Server 2003.

It makes sense. WIN XP x64 is based on Win 2003 x64.

It appears that the memory leak exhausts the system paged pool. We've had a couple servers hang up with event id 2020. Also I should have mentioned the boxes I am seeing this on are 32 bit, not 64.

Right now I'm backing off to the most recent version without the service.

Which version is that x16wda ?

I can't quite remember, did the service debut in 3.8?

I had 3 running Windows XP computers nonstop over 3 days...no luck with memory leaks :-( .. I'm still investigating.

Could you please try the http://systemexplorer.net/forum2/discussion/1706/system-explorer-3.8.7-beta-1 version? We can't still reproduce this bug.

Let me know. Thanks

did not help. looks like private space, not np pool as i thought earlier. i have a couple screen shots, can i email them? they show private storage up to almost 1gb, and odd results on the popup display, cpu load from the program. also could not kill the systemexplorerservice.exe. having to button the server now. :-(

Please email it to admin@systemexplorer.net. Thank you

Could you please try version http://systemexplorer.net/forum2/discussion/1709/system-explorer-3.8.7-beta-2. Thank you

I installed Beta 2 on my work utility pc (not a server this time) and have been monitoring memory use. After I started it up and it had time to stabilize, the memory use showed as 4252kb. Currently, after 4 hours running (without doing anything significant on the box), the memory use is up to 5020kb. I'll check again later tonight and in the morning.

as of 9:45 (roughly 9 hours running) memory is up to 5328.

as of 6am memory is up to 7460k and the vm size, which had been steady at maybe 28mb or so, is up to 41mb.

i have not done anything with this box since starting beta2, although at 2am I have a task that runs a number of batch fastcopy steps.

do you tag different mallocs [or whatever] with different tags? i could run memsnap periodically and see what tags are growing.

This is much better result compared with previous versions ;-). I think there will be just some memory fragmentation and some filled caches, beyond actual increase...

Could you please make memory dump of process and send me for analyze ?
See http://blogs.msdn.com/b/junfeng/archive/2008/06/19/getting-a-full-memory-dump-for-a-process.aspx

Thank you

The dump is on its way now.

I had not run across ntsd before, thanks for the mention!

thank you

I, too, have had problems running System Explorer on both Windows XP 64 and Windows Home Server 2008 (based on Windows Server 2003 32-bit) and see the memory continue to grow until it locks up the machine. It also eats 20-30% CPU after a while of running and growing.

I tried the 3.8.7 beta 2 and it did nothing to mitigate my problems. After about 4 hours of running on my WHS server it had over 1.5GB of memory in use and was running about 25% CPU utilization. I killed it and wonder what I should try next?

You can also make memory dump, compress it and send to admin@systemexplorer.net

See:
http://blogs.msdn.com/b/junfeng/archive/2008/06/19/getting-a-full-memory-dump-for-a-process.aspx

2spknapp: Are you sure you had running service from new 3.8.7 Beta 2 version? Did you uninstall previous version?

Next version of SE is available here: http://systemexplorer.net/forum2/discussion/1710/system-explorer-3.8.7-beta-3/p1

I have loaded SE 3.8.7-beta-3 on my WHS server and will report back. I will send you a memory dump if I still encounter problems.

After running SE 3.8.7-beta-3 on my WHS server for only three hours SystemExplorerService.exe was up to 1GB memory usage. I am sending you the fulldump of the service via your email address.

I tried to send you the fulldump file zipped up, and I got this error message instead:


Your message did not reach some or all of the intended recipients.

Subject: foo.zip
Sent: 4/15/2012 8:22 PM

The following recipient(s) cannot be reached:

'admin@systemexplorer.net' on 4/15/2012 8:59 PM
550 message too large.



The zip file is 100MB, How do you want me to get it to you?

Could you use service yousendit.com ? Thanks

I changed some code...could you please try Beta 4? http://systemexplorer.net/forum2/discussion/1711/system-explorer-3.8.7-beta-4/p1

Thank you!

Loaded SE 3.8.7-beta-4 on my WHS server and will monitor throughout the day.

After 3 hours on my WHS server, systemexplorer.exe is only using 7,840KB memory and 10,696KB VM size while the systemexplorerservice.exe is only using 9,564KB memory and 7,720KB VM size. When it looked like it was OK on my WHS server, I also installed it on my Windows XP 64-bit system (where I saw memory leaking there, too) and after 3 hours systemexplorer.exe is only using 8,880KB memory and 15,744KB VM size and systemexplorerservice64.exe is only using 5,944KB memory and 3,392KB VM size.

I think this might have fixed the problems I was seeing with the memory leaks on both my WHS server and my Windows XP 64-bit PC.

Thank you very much

problem fixed
thanks

looks good from my end as well so far, will put 3.8.7 on another server when i can be around to watch it for a day :-)