Roll20 stops responding on Chrome when editing spells or Rolling

I noticed this issue starting on Friday. Whenever I tried to edit my spells by "Unlocking" them to delete them Roll20 would stop responding. Today while playing the issue persisted and also occurred whenever I would roll Initiation, Hit Die, or any kind of check. Damage and hit on spells were unaffected. This issue happens in all games I involved in with all characters. My Chrome Version number is 54.0.2840.71 m and apparently I have an update to apply.  I currently run Windows10 I'm going to update Chrome and post back with what happens. 

Updated Chrome to Version 54.0.2840.87 m. Issue persists. 

which sheet are you using?

I'm using the SRD5 Roll20 Sheet

Is it only you experiencing this, or are other players in your campaign as well? If it's only you, could 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!) Thank you! Note, I'm not a mod, just passing along some generally helpful advice.

I'm having the exact same issue tonight. (Not a part of Redlin's group).  All dice rolls I've attempted tonight (no dmg or hit attempts so far tonight, though) from my character sheet freeze roll20 (music, webcam, etc.) for 5-10 seconds and then the roll completes. I'm using the same browser (perhaps updated) with the same add-ons as usual, but my group hasn't played for approximately 3 weeks when I had no issues. Google Chrome Version 54.0.2840.87 m

Going through my addons I figured out that disabling the LastPass addon fixed the issue.  Hope this discovery can help others with the same issue. 

Disabling LastPass fixed it for me also. Thanks for the heads up, Redlin.

Great! I'll mark this as resolved; feel free to open a new thread if you experience any other issues.