Memory overflow when using Browser

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!

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?

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?

IE, Firefox, Chrome

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

I will try and let You know.

did not work :(

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

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.

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

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

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

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

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

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

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

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

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 :)

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.