Fences & RAM

from Stardock Forums

I have searched everywhere but no one appears to have this problem. I have Fences in use on 2 different computers. One installation on W7 runs fine, but the other installation on XP is grabbing RAM. I use a CPU meter, and for no reason the RAM usage will start to climb rapidly. Within about 30 seconds, the usage has risen from 30% up to 100%, but within a few seconds of reaching the max, it dives back to 30% instantly. It is then ok for several hours, but then for no reason it will repeat the cycle. It is definitely Fences that is doing this. I uninstalled Impulse to see if this was the cause, but it still happens. The version I have is 1.00.2787. Any ideas, because when this happens, everything else freezes until the cycle has completed.

3,846 views 3 replies
Reply #1 from WinCustomize Forums Top

I have Fences running on an XP Home 32 bit and Win 7 Home Premium 64 bit system and don't see that problem.  I wouldn't think Impulse would do that. 

It sounds like you have a program running in the background like maybe a security or anit-virus program.  Other that the different OS's on the two computers what else is different?

Reply #2 from Stardock Forums Top

They are completely different computers and set ups. Too many differences to list, but the computer that is ok has probably 10 times the amount of programs running. It's not another program doing this. Task Manager clearly shows Fences.exe is the program that is grabbing the RAM. I should add that there is 2gb of RAM and I have never seen any program grab that amount for anything.

Ashes of the Singularity II
Reply #3 from WinCustomize Forums Top

Okay, then could it be whatever you have put into Fences on the one computer?  Fences it self shouldn't use ram.

If you don't have anything put in a Fence that could be doing it I would try uninstalling Fences on the one computer (after moving the icons to the desktop) run a clean up program like CCleaner and reboot and reinstall Fences.  It might be the the download and install got messed up.

If the problem is still there then you should email support@stardock.com and explain the problem.