Locked

Flash Player 30.0.0.113 - Audio and Mouse Control Issues

New Here ,
Jun 07, 2018 Jun 07, 2018

Copy link to clipboard

Copied

flash version: 30.0.0.113

OS: Windows 10

Browsers : Chrome (Mozilla) 

In social game audio (inc. sounds) isn't playing

Mouse cursor doesn't move fluently

Views

616

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 07, 2018 Jun 07, 2018

Copy link to clipboard

Copied

Please provide direct link to game that is experiencing issues.

Also, please work through the Troubleshoot Flash Player games, video, or audio| Windows guide.

Thank you.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 07, 2018 Jun 07, 2018

Copy link to clipboard

Copied

game: Klondike on Facebook | Facebook

After the last (ver. 30.0.0.113) update of the flash player, the execution of the game code requires more CPU time (almost in 10 times, comparing to execution in flash player version 27). For example, in Adobe Scout, you could see that execution of system function "getTimer()" requires much more CPU time (approximately in 1000 times, comparing to execution in flash player version 27).

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 07, 2018 Jun 07, 2018

Copy link to clipboard

Copied

Thank you for the link and the additional details. Can you take a look at Performance Issues in Flash 30. ?  Your issue sounds similar to this one.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 07, 2018 Jun 07, 2018

Copy link to clipboard

Copied

Yes.  We've made a necessary mitigation for Spectre/Meltdown-style attacks that significantly increases the cost of calls to getTimer() (~100us).  This change isn't apparent in most content, but if you're calling getTimer in a tight loop, the impact pretty pronounced. The best solution is to modify the content to use getTimer() more judiciously.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 08, 2018 Jun 08, 2018

Copy link to clipboard

Copied

Thanks for the answers.

Performance Issues in Flash 30.  is the discussion for the same issue. I'll continue read that one.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 12, 2018 Jun 12, 2018

Copy link to clipboard

Copied

Just to be clear, the resolution of getTimer() is 1 millisecond.  The delay we introduced is about 100 microseconds.  This only becomes apparent when content is calling getTimer() hundreds or thousands of times within a single millisecond, when the value of those calls would never change.  

The folks at MIT implemented a nice cached timer approach for Scratch that addresses this, which you can see here:

Flash 30 performance changes by cwillisf · Pull Request #1396 · LLK/scratch-flash · GitHub

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines