We are getting reports from users throughout the Scratch (scratch.mit.edu) community of performance issues related to Flash 30. Upon a deeper investigation it seems as if the main event loop is running much more slowly even in simple tests, this may have something to do with hardware (GPU) acceleration, but more investigation is needed. Results of a single benchmark for Chrome on MacOS are included below, but we are seeing the impacts of these across all 200+ million projects shared in the Scratch online community. We have also been able to repro this on Firefox and Safari on MacOS. We will be testing on Windows shortly and will post results here once complete.
Flash Version - 29.0.0.171
Google Chrome (PPAPI)
Macintosh (OSX)
Flash Version - 30.0.0.113
Google Chrome (PPAPI)
Macintosh (OSX)
1 Correct answer
Because of the changes by Adobe which increase the cost of `getTimer` and related APIs, we have deployed a patch that resolves the issue by reducing calls to `getTimer` and gets our performance back to where it was before the release of Flash 30 in most instances. If you are curious, details of the patch are available here:
Flash 30 performance changes by cwillisf · Pull Request #1396 · LLK/scratch-flash · GitHub
Timely assistance from Adobe (particularly in narrowing down the source of our proble
...
27
Replies
AdChoices