Roll20 Crashes When Changing Pages

I have 2 large pages (going on 3) that are 100 x 100 and each the floor of a dungeon. If I load one 100 x 100 page then try to move and load the other 100 x 100 page, Roll20 crashes and says "Aw Snap!" on Chrome. I tried loading a 10 x 10 map in between the two 100 x 100 maps as a sort of buffer but it still crashes if I load one then any time during the same session try to load the other one. Can someone help me resolve this? What information do you need from me?

Hey Kastion Sometimes large maps can cause too much strain on the user's computer (even my gaming rig experiences this). Factor in dynamic lighting, advanced fog of war, a large amount of Character sheets or assets on the map itself and it really begins to bog the PC down. If you're sure that its not a case of overload, can you please carefully work through the first three 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 and anti-virus programs. Step 3: Clear your cache If none of the above succeeds, please thoroughly work through Step 4 . (Don't forget the complete Console Log!)

Step 1 Can reproduce the error 100% of the time in Chrome. Firefox doesn't have this issue. No crashing in Firefox. Step 2 No extensions installed on either browser. Step 3: Cleared my Cache and it didn't fix it. Moving on to Step 4. ( Also as a side note I remember reading a wiki post or forum post about optimizing settings for Chrome, can someone link that I can't seem to find it?)

I can move back and forth between maps with no crashes and no load time in Firefox. Anyone know any settings I a can adjust (probably related to max memory allocation for pages?) in Chrome to get this fixed in that browser? It works fine in Firefox.

You can change the memory allocation for chrome by adding "--max_old_space_size=4096" to the target of your chrome shortcut target. 

I gave up on Chrome. Maybe a staffer can come into my campaign as a GM and switch back and forth between the two dungeon floors to see if they can replicate the error but until a later date when I can use Chrome without errors (Like crashing from loading a map or getting an infinite loop warning in API Sandbox) I will be using Firefox. I suggest everyone use Firefox instead of Chrome. It is WAY more stable and less buggy even if it takes 10x more time to load up my campaign.

Franky H. said: You can change the memory allocation for chrome by adding "--max_old_space_size=4096" to the target of your chrome shortcut target.  I tried this and still get crashes when trying to load up two 100 x 100 maps in a row (or even not in a row just in the same session) I'm sticking with Firefox until a few more Chrome updates come out. Speaking of updates, I just updated Chrome and now there are no scroll bars (horizontal or vertical) in the campaign session browser tab. That put the final nail in the coffin. I've moved over to Firefox. It's so much better in terms of stability.

I switched to Firefox when Quantum was released, at least for running the game. So much snappier.

keithcurtis said: I switched to Firefox when Quantum was released, at least for running the game. So much snappier. I've only been using it for about 2 hours but I've already imported everything from Chrome and customized it and it runs so much better on the Roll20 App I'm just at a loss for words. No crashes. No slowdowns. No bugs. No API Sandbox Infinite Loop warnings. I dare say I might turn PageFX back on and see how it manages in Firefox. Definitely going to get all my players to switch browsers for playing the campaign at least.

The only drawback that was a near deal-killer for me was that Firefox will not allow Javascript Bookmarklets. But the tradeoff in speed is worth it.