• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Memory Leak for WHS-2011 Dashboard?

Has anyone noticed something like this? I'm wondering if it could be the result of an add-in component, like "Lights Out" or "Advanced Admin Console." My first guess is anything that has a constant monitoring aspect with frequent updates -- like Lights Out.

The server has 4GB of RAM. If I leave Dashboard running, if only on the server desktop directly as opposed to the client, memory consumption climbs to 70 or 80% over time. If I close Dashboard, memory usage drops to 20%, and opening it again adds just a little (but it would increase over time if Dashboard left running.)

I've had Dashboard crash or enter a "Not Responding" episode if left running for good part of a day.
 
I don't have any addons. I never leave the dashboard open. System 100% stable.

If you'd like I can open Dashboard and leave it open for a couple days to see if it causes any problems?
 
I don't have any addons. I never leave the dashboard open. System 100% stable.

If you'd like I can open Dashboard and leave it open for a couple days to see if it causes any problems?

You're welcome to do that, and we can compare notes. Otherwise, the WHS-2011 system I've built is rock-stable. It gave me a "not responding" note on Dashboard after I'd left it running (the Dashboard) for good part of a day. RAM usage before the "no response" was at near 100% -- dropped to 20% after ending the program in task manager. Started it up on the spot -- everything was fine.

I'm using:

Lights Out
Advanced Admin Console
StableBit DrivePool

Lights Out seems to be constantly polling the client machines on the LAN, because it's set up to monitor them. Of course, it's STILL polling the machines when Dashboard isn't running, and memory usage then remains low.
 
Back
Top