You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@NeilFraser made an initial investigation and reported:
First finding is that it's lightning quick in Firefox. No issues there. Likewise, Safari is smooth.
Google Chrome on the other hand is problematic. First it's very choppy (but usable). An examination of the console shows that most of the CPU is going to 'rendering', not Blockly's JavaScript. But leave the page alone for a few minutes, and it becomes utterly unusable.
To Reproduce
See discussion in linked forum post above.
Desktop (please complete the following information):
OS:
Browser: Chrome
Version: 9.1.0
The text was updated successfully, but these errors were encountered:
We've seen this behavior for quite a while in App Inventor and we're using a (really) old version of Blockly. Firefox performs much better for some reason and it seems as though it is a regression in Chrome. I could probably go back in our community history to find the point at which the performance degraded, but it's been an issue generally for a while.
Describe the bug
A user in the Blockly forum reports Blockly being unusable with >5k blocks.
@NeilFraser made an initial investigation and reported:
To Reproduce
See discussion in linked forum post above.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: