Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

memory leaks when Solarwinds left too long

I am seeing regular memory leak problems when runnign solarwinds for more than about 12 hours on an IE interface. This is an issue when one is leaving up a chart to monitor over a period of time.

Typicaly results are to come back and find an error "Out of memory at line: 1166" or similar. the line number varies.

Updating IE or using a different browser is not really an options due to corporate policy.

Any thoughts?

Find more posts tagged with

Accepted answers

All comments

Donald_Francis

Not saying you are wrong but I have myself never seen that and I use all 3 major browsers. And I as well as many of my co-workers leave it up and running for 8-10 hours regularly. In fact we have a few places that use large screen TVs to display SolarWinds dashboards (I have 2 where I am) and they do not have that issue either and they will run for days or weeks or longer.

As I see it the Browser App and the OS are in control of your memory usage not the webpage. Have you seen this on multiple machines?

shread

Thanks for the feedback. Yes I have seen it on multiple machines. Typically when left overnight. It only occurs when leaving solarwinds up and monitoring a device or some netflow reporting that I have seen.

Donald_Francis

This may sound stupid but I have to ask it. Have you actually looked and seen that a particular process (hopefully just the browser) has eaten up all the RAM?

If it is a true leak and not over utilization you may not but I was just curious.

MarieB

Shread--

If you don't get this resolved from this thread and you are on active maintenance, open a support ticket.

When you open a support ticket, would you:

--Reference this thread to Support.
--Post back here with a case number.
--Post any solutions you get from Support.

Many thx,