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 .
×

Updating tokens slows down Roll20

I have noticed for some time (maybe 1-2 months) that updating tokens one after the other slows down Roll20. I noticed this particularly recently when I updated the hp for about 20 tokens during prep. After I loaded into Roll20, opening the settings of first couple of tokens was very responsive, but soon, each one I opened would seem to freeze before I could edit any values, getting longer and longer with each subsequent token. The settings window would appear immediately after I double-clicked the token, it's editing the value that gets delayed. I have seen this issue also occuring when I just update the token radial bubbles when I ran combat and updating hp. The features show up immediately after I click on a token, but I can't edit the bubbles until a bit of time passes. I last tested this today, using Firefox 98.0.2.
1649388726

Edited 1649396880
One thing to try is to check your settings in Firefox: Under Preferences > Privacy and Security, under "Forms and Autofill," make sure "Autofill addresses" and "Autofill credit cards" are both unchecked. I had the identical issue two years ago and unchecking "Autofill addresses" turned out to be the solution for me. Please let us know if that works for you, or if there is something else going on. Edit: Yay! I'm glad that helped. Thank you for posting the solution.
Sarah R. Cohen said: One thing to try is to check your settings in Firefox: Under Preferences > Privacy and Security, under "Forms and Autofill," make sure "Autofill addresses" and "Autofill credit cards" are both unchecked. Thank you!  I only had "Autofill addresses" checked at the time, and just unchecking that one seemed to have fixed the issue.