I'm not sure what you mean by "crashing FoxWeb". Are you referring to individual channels hanging and being restarted? If yes, then the back action is causing a request to be sent to the server and that request appears to be causing an error in one or more of your scripts, causing the channel to hang. This will usually not be logged in the FoxWeb error log, but should have an associated entry in fw_start.log, indicating that the FoxWeb Channel Controller restarted the channel after it was unresponsive for longer than the script timeout.
Moreover, if users refresh the problem page multiple times, they can cause a temporary situation where FoxWeb has no available channels, because they are all in an unresponsive state, but still within the script timeout.
FoxWeb Support Team
Sent by Joe Goldsmiith on 11/18/2014 11:21:17 AM:
Starting back about a couple of months ago my users have been crashing FoxWeb receiving the black broker message. The cause of this seems to be when users on a page press the browser's back page button on any browser and on either a PC or Apple. No error was logged in the Control Center.
I use Session.GetVar on every page to keep track of who has logged in and what they are able to see on a page. I have used this technique for many years without problem and just toss in this feature as a thought to explore. I really don't think this causes the issue.
Has anyone else encountered the issue of the browser back page button and if so was there a fix?