Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Token Movement Measurement Crashes Firefox Browser

It's never happened before, but as of recently, one of my players tried to track their token's movement (the one where you press/hold "Q" as you move the Token) and it caused my browser (and apparently the other players' browsers) to stall immensely, freezing up in huge gaps and even crashing.  I tested it again on my end and the same thing. We did it a 3rd time with a different player and same thing. So we pretty much had to stop using it entirely, which sucks because it's never done that before in our games and we figured to let Roll20 know it seems like some kind of bug maybe causing it.
Howdy! Okay, I wanted to try and replicate this (because firefox is my go to browser!) and I wasn't able to, which is strange. I'm assuming this was happening in a non-Jumpgate game- but let me know if I'm wrong. Does this still happen to you if you try to do this in a new, blank game?
Katie Mae🔮 said: Howdy! Okay, I wanted to try and replicate this (because firefox is my go to browser!) and I wasn't able to, which is strange. I'm assuming this was happening in a non-Jumpgate game- but let me know if I'm wrong. Does this still happen to you if you try to do this in a new, blank game? It was a Pathfinder game we've been running fine for over a year and one of my players was tracking his token's movement at our last session on Tuesday night when it first happened. I didn't understand what was causing the browser to start crashing until I did it myself, and then another player did it later on for the 3rd time and we, thus, realized the cause.  Firefox just went super laggy, with pop ups saying the browser was overloaded or something to that effect, and it didn't even want to close the tab out. I had to close Firefox and restart it and re-enter to fix it. It also didn't just happen to me, as one of my other players had to close out Firefox and re-enter because it had happened to him as well.
I've had this happen as well. I use Chrome, but some of my players use Firefox and we all experienced the same behavior at the time. I wanted to experiment with not using the grid for measuring distance and movement, but that buggy experience threw that plan out the window and we haven't tried it since.