Issues with Unresponsive Scripts?

The issue here is that we load SOOOO much information into the Atlas, it takes a while to load it all. Most browsers aren’t used to running such rich applications and are tuned to deliver lightweight-focused applications as quickly as possible. When the browser takes a little longer than expected to run a page, it automatically thinks something is wrong and is prompting you whether or not you want to continue with it or not.

There is a setting in Firefox that will increase the amount of time to let scripts run. I suggest giving this a shot:

To tell Firefox to let the script run longer:

1. In the address bar, type about:config and press Enter.
• The about:config "This might void your warranty!" warning page may appear. Click I accept the risk! to continue to the about:config page.
2. In the about:config page, search for the preference dom.max_script_run_time, and double-click on it.
3. In the Enter integer value prompt, type 20.
4. Press OK.

I’m pretty sure that this will take care of it. Chrome has a max_scirpt_run_time of 20 and I don’t get this message. Since downloading Firefox and testing, I have seen the window a few times. I’m going to leave my setting at 0 to see if I get the pop-up and then change it to see if it fixes it. I suspect it does.

Some other things to consider:

1. Some hours are busier on the Atlas than others. Just like rush-hour-traffic, data has to flow to/from the Atlas on the same interstate. If there is more traffic than other times of the day, it does get slower. The server that receives/sends data has to process the information and send it on the same highway and if the highway starts getting backed up, it can cause some information to get delayed back to you and thus, cause scripts to run longer. Rush hour for the Atlas is between 1pm and 3:30pm.
2. Try and limit your sessions to an hour or less. Running the Atlas for longer periods of time can cause some services/scripts to become unresponsive. We cannot leave connections open to users all-day. The server will close a connection to a user that has been unresponsive for a couple hours to free up resources for others trying to get access. If we left connections open for everyone that loaded the application and left it on all day, we would run out of resources for those that need to do a quick task.
3. Save your project. If you haven’t already, sign up for a free ArcGIS Online account and use this for saving your project.
4. Utilize our themes for setting up your mapping content quickly. Consider suggesting new themes that could help you set up a map that you find you are routinely creating.
5. Be patient with us… We are working with extremely limited resources and are trying to squeeze a full glass of juice out of a single orange. We are doing our best to keep the Atlas running for as many users as we can. We apologize for any inconveniences it causes, but cannot guarantee its performance 24/7.