I have just realised that I posted an update to this issue on a related thread by accident. Double posting so that the information sticks with the original issue of Roll20 Freezing up. -- REPOST -- Further observations from an absolutely lamentable session this evening. I have fully switched browsers to Chrome because it seems to perform better than Firefox at the moment and I thought things were going well for the first 5 minutes of my sessions. Then all the problems from the previous session came back. We are in room 30a of Level 10 of the Roll20 Dungeon of the Mad Mage module. My over confident players had alerted the entire room and were facing a horde, but I do not think the nature of the room nor the number of tokens is the issue as it presented multiple times in the following encounter in 26 with fewer tokens. The main symptom that I can diagnose is that my Canvas stops rendering I can tell the interaction engine is still processing events because I can select tokens in places where I cannot see tokens in my view port. Any panning or zooming is reflected on the position / length of the scrollbars, but the canvas jumps to the view it showed at the start of the operation. If I have a token selected at the time of failure I can type into the hit point box and alter HP, but the values do not change in my view (though they are persisted to the model as they are amended on refresh). I do not want to pop my console during play because I am recording the sessions, and after the game is over I am unable to replicate the problem so it must have something to do with concurrent actions happening from my 3 players and myself. During this session one of my players pointed out one token on the elevated ledge in 30a which did not appear on my screen, and I am certain from my console logs that there are at least 18 other lost tokens because I have that many resource load failures. (Could not load image from ...) However as my players cannot see the GM layer, the vanished ones could be hiding there in ambush. I am just throwing darts at the wall with ideas which I think might help but if any of the following could be implemented it might help: - A tool which iterates over every token on the canvas and adds one of the colour dots Status Icons to it so that the site is forced to render even if the token's image cannot be loaded (although this would break if your rendering step just borks and doesn't draw in the event of a resource load fail) - A list of all tokens on the map with the ability to click the list and cause the token to be selected in the canvas and the view port pulled to it. - A key bind to select next token and pull the view port to it. (this would be torturous to keep mashing given the large number of tokens, but at least it would mean no new UI to code in) - A catch for the URL load failure, which deletes the failing token from the database entirely. Harsh, but at this point I cannot see any of them so they might as well be deleted for all I care. Maybe these corrupted tokens are what is killing the canvas. I suspect a lot of these suggestions have been implemented by people with API access, but they would need giving to lesser GMs as, at this moment, I am having to tell my players I want to put my campaign on hold because I cannot face having to refresh the page once every 20 seconds and wait for everything to load up again only for it fail a few moments later.