Closed hackofalltrades closed 11 years ago
Since Facewall is rendering a lot of images, it can use a lot of memory. We have noticed this can crash the browser in extreme cases. My recommendation is to try lowering the value of refresh_seconds
in constants.coffee from 30 * 60
(30 minutes) to 6 * 60
(6 minutes). Although we haven't done thorough testing on this, refreshing the page every once in a while seems to prevent the browser from crashing due to memory-related issues.
Depending on the configuration of your machine and the number of employees you have, the performance of the Facewall will vary. At HubSpot, we run the Facewall on three 1920x1080 monitors in our lobby, driven by one Windows machine with three ATI graphics cards with HDMI outputs. And we have about 600 employees. This seems to work fine for us, but we're certainly intersted to hear if other people's experiences differ. Good luck!
I appreciate the response. I will try the change you suggested and upgrade the hardware if that doesn't do it. I will let you know! Thanks.
Changing the constants.coffee to 6 minutes didn't fix it but gave me some insight! It seems to be crashing every 6 minutes now. It makes sense because it was crashing every 30 minutes before. I set it to refresh every 2 weeks and expect it to crash then. If I refresh the browser manually it works with no problem. Not sure what is going on there but I've got a workaround in place.
Thanks!
I am running this on a few systems. Is there a recommended browser/OS to run this on as Chrome seems to crash for Mac regularly.