New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Memory overflow when using Browser

Votes:

0

Your Vote:

Up

Down

We create a alarm map and it is permanently showing in a browser window. In a few hours the browser crash down, because the memory is overflow. It is the only task that run on the system and it doesnt matter what kind of browser we use.

browser-crash memory prtg-network-monitor

Created on Nov 3, 2016 8:18:45 AM by  Tobias Walther (0) 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Problem

Browsers are crashing frequently within a few hours when displaying a map. It can be reproduced in different browsers.

Workaround

Please try to use incognito tabs instead of normal browser tabs. The memory usage for normal tabs seems to increase over time where the incognito tab is much more stable and uses less memory:

Normal Chrome Tab

TimstampMemory Usage
13.02.2017 08:29:321.158 MByte
13.02.2017 08:30:321.183 MByte
13.02.2017 08:31:321.228 MByte
13.02.2017 08:32:321.227 MByte
13.02.2017 08:33:321.481 MByte

Incognito Chrome Tab

13.02.2017 09:05:02664 MByte
13.02.2017 09:04:32703 MByte
13.02.2017 09:04:02647 MByte
13.02.2017 09:03:02662 MByte
13.02.2017 09:02:32698 MByte
13.02.2017 09:02:02663 MByte
13.02.2017 09:01:32699 MByte
13.02.2017 09:01:02651 MByte

The latter one seems to be much more stable and should make the dashboard itself run stable without frequently crashing.

Status

DateStatus
13.02.2017Investigating issue
11.04.2017Issue closed, cannot be reproduced

Created on Feb 13, 2017 8:30:37 AM by  Stephan Linke [Paessler Support]

Last change on Apr 11, 2017 8:19:12 AM by  Stephan Linke [Paessler Support]



20 Replies

Votes:

0

Your Vote:

Up

Down

The only way around this would be to kill the browser process periodically and restart it. The following script will call the given map URL in Internet Explorer and make the browser go into fullscreen mode:

param([string]$mapurl = "https://www.paessler.com/");

# Stop the process first
Get-Process iexplore | Stop-Process

# create a new instance of the browser
$browser = new-object -com internetexplorer.application

# enable fullscreen
$browser.FullScreen = $true
$browser.Visible    = $true
$browser.Navigate($mapurl);

Simply save the script on the host that is used to display the map. Then you create a new scheduled task with the following settings, the path may vary of course. The screenshots are in German, but that should work for you :)

Note that if you're using multiple monitors for the map display, this probably won't work, since you can't move the window to the corresponding screen :( Let me know if this works out for you!

Created on Nov 4, 2016 10:55:22 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

we use two monitors and several maps, they toggle in time map creating and monitoring in a browser is one of the feature from PRTG and this should be the solution?

Created on Nov 7, 2016 7:47:39 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

Well I've only seen this in one installation so far, so it's working for many other users. What browsers have been tested so far?

Created on Nov 7, 2016 8:05:42 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

IE, Firefox, Chrome

Created on Nov 7, 2016 8:08:15 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

You could try starting Chrome with the following arguments, it should result in less memory overhead: --process-per-site

Created on Nov 7, 2016 8:24:35 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I will try and let You know.

Created on Nov 7, 2016 8:39:40 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

did not work :(

Created on Nov 11, 2016 6:50:24 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

Did the browser actually get restarted once every hour? And it was still crashing due to RAM being full?

Created on Nov 11, 2016 9:57:58 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

The RAM is full in 4-5 hours and the browser crash. We have 3 maps on two monitors. One map in one browser window on monitor one and two maps in two Tabs on browser window two on monitor two.

Created on Nov 11, 2016 10:12:13 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

Forget my last reply...unfortunately, I don't have any ace upon my sleeve :(

Created on Nov 11, 2016 10:24:56 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

i have a snapshot from our Chrome session for you, there you can see, when you search in the "detached dom treee" which function which variables will keep open and let the memory full

Created on Nov 14, 2016 7:28:04 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

Could you send it to [email protected], referencing to this thread? Then I'll forward it to our developers :)

Created on Nov 14, 2016 7:55:38 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

i can not, because your Server did not accept the size from the mail :(

Created on Nov 15, 2016 5:43:10 AM by  Tobias Walther (0) 1



Votes:

0

Your Vote:

Up

Down

Received it via the ticket - we'll take a look at it :)

Created on Nov 15, 2016 11:09:59 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

we have the same problem displaying several maps on out monitor dashboards. Any current browser IE, chrome, firefox runs out of memory after some time, crashes and need the be restarted / reloaded. This started with a version upgrade of paessler some months ago, did not change with the last versions and results in restarting the browsers at least every morning, sometimes throughout the day

Created on Dec 19, 2016 9:29:27 AM by  Franz Leippert (0) 1



Votes:

0

Your Vote:

Up

Down

Are you using the 3d globe object on the map?

Created on Dec 19, 2016 9:45:26 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

no, the maps mostly contain about 20 sensors displayed as "Status Icon on Status Related Background" and the same number of "Default Icons A", used ( and displayed ) sensors are mostly tcp-port-Monitors ( 320x, 1352 ) and a few using http-sensors

Created on Feb 9, 2017 7:30:15 AM by  Franz Leippert (0) 1



Votes:

0

Your Vote:

Up

Down

Hm, did you consider using a raspberry pi and with Raspian instead? This is a good tutorial and our dashboards work just fine with that :)

Created on Feb 9, 2017 8:15:53 AM by  Stephan Linke [Paessler Support]



Votes:

0

Your Vote:

Up

Down

no real option - first of all Raspberry does not fit to our standards and we have 2 nonitors on 1 PC to display. Map-display worked for several months with older paessler versions without any problems but now we have to restart crashed browser sessions every morning. Very bad is the situation when the browser does not crash but just freezes and the map is still displayed. so if there are any changes/system fails , they are not displayed to the stuff so maps are worthless.

Created on Feb 9, 2017 12:49:30 PM by  Franz Leippert (0) 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Problem

Browsers are crashing frequently within a few hours when displaying a map. It can be reproduced in different browsers.

Workaround

Please try to use incognito tabs instead of normal browser tabs. The memory usage for normal tabs seems to increase over time where the incognito tab is much more stable and uses less memory:

Normal Chrome Tab

TimstampMemory Usage
13.02.2017 08:29:321.158 MByte
13.02.2017 08:30:321.183 MByte
13.02.2017 08:31:321.228 MByte
13.02.2017 08:32:321.227 MByte
13.02.2017 08:33:321.481 MByte

Incognito Chrome Tab

13.02.2017 09:05:02664 MByte
13.02.2017 09:04:32703 MByte
13.02.2017 09:04:02647 MByte
13.02.2017 09:03:02662 MByte
13.02.2017 09:02:32698 MByte
13.02.2017 09:02:02663 MByte
13.02.2017 09:01:32699 MByte
13.02.2017 09:01:02651 MByte

The latter one seems to be much more stable and should make the dashboard itself run stable without frequently crashing.

Status

DateStatus
13.02.2017Investigating issue
11.04.2017Issue closed, cannot be reproduced

Created on Feb 13, 2017 8:30:37 AM by  Stephan Linke [Paessler Support]

Last change on Apr 11, 2017 8:19:12 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.