Game won't load after enabling AFOW on a large map

On a large map, I had dynamic lighting enabled and then I also enabled AFoW. After doing this, the site hung.  I haven't been able to relaunch my game in several days since. When I launch the game, it sometimes loads the chat log and macros, but usually hangs with a black tabletop and "Loading..." and "Determining Size Scales..." Sometimes it hangs on "Crafting Spells List..."  My browser usually prompts me about a web page that is slowing down my browser. This happens on two different computers, both using chrome. It also happens with firefox. I am pretty sure my problem is related to the AFoW on the map it's trying to load, so what I'd like is any workaround to get into my game so I can load the map and disable AFoW on it. Thanks!

Hello Arik F., I'm sorry to hear that you're having issues with the site. To rule out possible issue,  please carefully work through these steps of our guide to  Solving Technical Issues : Step 1: Make sure to use the right browser Please check if these issues persist when using both Chrome  and  Firefox. Step 2: Ensure that there are no extensions/addons interfering with Roll20 Please disable  all  add-ons/extensions. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through all of the requested information in  Step 4 .  (Don't forget the complete Console Log! Thank you!

The above steps are essential in the resolution process. If you do want to try a workaround, assuming the map in question does not have the player flag on it: Create a Dummy Account . Promote it to GM. Log in with the dummy account, which will not load on the problem page. Edit the settings on the problem page. Try logging in again with your normal account. However, if the problem turns out to need dev intervention, the steps Rainflame gave above are needed, especially Step 4.

@Rainflame, thank you for the link to the troubleshooting steps. I didn't see the benefit of pursuing that level of formality, given that I know what caused the problem. @keithcurtis, thanks, that worked!