I created a screen that shows two web pages along with Homeseer data. One page is local traffic and the other is my weeks itinerary.
Both pages are refreshed every 20 minutes to make sure I have current information.
The result is that the page runs correctly for between 12 and 18 hours and then I get an out of memory error that kills the client. I believe it's because homeseer still uses IE to render web pages and that browser has a known memory leak that will never be fixed. Has anyone found a way to use chrome or firefox to render html in Homeseer? Or some other work around that gets passed this issue. I tried even creating a screen that I could switch to for a moment and then go back, but Homeseer doesn't really close a screen even if you say show a screen by itself.
Both pages are refreshed every 20 minutes to make sure I have current information.
The result is that the page runs correctly for between 12 and 18 hours and then I get an out of memory error that kills the client. I believe it's because homeseer still uses IE to render web pages and that browser has a known memory leak that will never be fixed. Has anyone found a way to use chrome or firefox to render html in Homeseer? Or some other work around that gets passed this issue. I tried even creating a screen that I could switch to for a moment and then go back, but Homeseer doesn't really close a screen even if you say show a screen by itself.
Comment