Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Stop inactive tabs from throttling down/ timing out

  • 2 odgovora
  • 1 ima ovaj problem
  • 15 prikaza
  • Posljednji odgovor od mikeyfila

more options

Hi I run a program called nodered on a raspberry pi in docker. I use a browser to reach the user interface via lan. If that tab sits in the background too long (~5 min) the connection with the server resets and resets the gui.

I lose all current debugging information and any unsaved changes. Saving the page will stop the lost progress but not the current debugging. In other words just saving the page each time will only solve 1/2 of the problem.

Is there anyway to keep a background page active so it doesn't reset after a few minutes?

https://nodered.org/

Hi I run a program called nodered on a raspberry pi in docker. I use a browser to reach the user interface via lan. If that tab sits in the background too long (~5 min) the connection with the server resets and resets the gui. I lose all current debugging information and any unsaved changes. Saving the page will stop the lost progress but not the current debugging. In other words just saving the page each time will only solve 1/2 of the problem. Is there anyway to keep a background page active so it doesn't reset after a few minutes? https://nodered.org/

Izmjenjeno od mikeyfila

Svi odgovori (2)

more options

You can try to adjust some keepalive prefs on the about:config page to see if that works.

more options

Hi thanks for the response. I should have mentioned I adjusted everything I could find about background tabs and java script I could find.

I changed them to -1. This was the time out setting for the active tab pref. I assume that means infinity? It didn't make a difference. Do you know if -1 is just that, infinity? or should I just be using really large numbers?