New Participant

Answered

Error in Flash Player 30

Forum|Forum|7 years ago
June 7, 2018
3 replies
6374 views

Hi,

I'm trying to load one of my games using Flash Player 30 in Chrome. The game errors with the error message "ArgumentError: Error #3806" and fails to load. I was able to load the game on Firefox running Flash Player 29 but as soon as I manually upgraded to Flash Player 30 the game fails to load.

Is there a known issue which would cause this issue or can someone point me in the correct direction to file a bug! The game has been working correctly for nearly 4 years so I'm hoping that Adobe can fix the issue in Flash Player since an update to the game will be difficult.

You can see the issue here: Play SAS 4 - Ninja Kiwi

Regards,

Alan

3806

This topic has been closed for replies.

Correct answer jeromiec83223024

Thanks for the head's up (and for taking the time to file a bug).

We don't like to break backwards compatibility (and we rarely do it), but security is our highest priority. In this instance, we chose to disable functionality in order to protect users against vulnerabilities in a pretty big chunk of CPU hardware currently in the market. We chose this specific approach very carefully, to ensure that the impact to the average user would be minimal. This was the most surgical change we could make.

While it's possible to re-enable this functionality on the client, it increases their attack surface. We're recommend talking to the game developer to see if they can eliminate the use of shared ByteArrays.

You can find additional details in this blog post:

Spectre / Meltdown Mitigations

S

sy56595285

New Participant

Multithreading without shared memory is 99.9% useless.

It wasn't very useful with shareable bytearray: starting workers is extremely expensive and you had to waste time for encoding/decoding objects to bytes, but was still helpful for huge tasks.

Now even this possibility is lost. Force enabling feature is not an option because client organizations won't mess with that, and you can't just set it in swf embed code on the page.

All the time to make flash multithreading work is now just wasted, plus time needed to rewrite code back.

Security? This change can neither save flash player reputation, nor can it really protect users from hardware vulnerability.

Robert Mc Dowell

Braniac

"Force enabling feature"

you mean "force disabling a feature"....

Everyone knows how computers, smartphones and all electronic devices are not and will never be 100% secure.

People who think that the fault is always Flash are just ignorant and morons.

Now mitigate is always better than not do anything.

S

sy56595285

New Participant

No, I mean enabling. Existing installations use it. Flash player update just breaks important functionality.

You can add 'EnableInsecureByteArrayShareable=1' to mm.cfg to restore the feature, but it's likely not doable in practice on all the machines/networks which require it.

This vulnerability is minor risk. Killing functionality is a real trouble. Probably everyone for whom security was the primary concern already abandoned using flash or never used it, so I guess this 'better mitigation' affects only those who need shareable arrays more than minor theoretical security gain.

Robert Mc Dowell

Braniac

alanc78729854

the website shows an AS error for me:

Error #2044: Unhandled error:. text=Flash IMA sdk is deprecated.

at com.google.ads.ima.api::AdsLoader/createSdkLoader()

at com.google.ads.ima.api::AdsLoader/load()

at com.google.ads.ima.api::AdsLoader/invokeRemoteMethod()

at com.google.ads.ima.api::AdsLoader/requestAds()

at ima3_preloader_1_4_fla::MainTimeline/Initialize()

at ima3_preloader_1_4_fla::MainTimeline/frame1()

jeromiec83223024

Community Manager

This isn't our bug.

It looks like the content provider is using a Google library for Interactive Media Ads which is no longer supported by Google. The content provider also doesn't handle the case where calls to that library fails, hence the unhandled error. It looks like they'll need to change their ad insertion stuff.

Error #2044: Unhandled error:. text=Flash IMA sdk is deprecated.

alanc78729854Author

New Participant

Hi,

We know about that error but it doesn't affect the normal loading of the game. We see the same error in FP29.

Hopefully we'll be able to get an update out to let the game work with FP30

Regards,

Alan

alanc78729854Author

New Participant

I've added a bug to the official bug tracker although I suspect that the issue won't be fixed by Adobe since it appears that certain APIs have been deprecated with no warning. You can see the issue here: Tracker

jeromiec83223024

Correct answer

Community Manager

Thanks for the head's up (and for taking the time to file a bug).

We don't like to break backwards compatibility (and we rarely do it), but security is our highest priority. In this instance, we chose to disable functionality in order to protect users against vulnerabilities in a pretty big chunk of CPU hardware currently in the market. We chose this specific approach very carefully, to ensure that the impact to the average user would be minimal. This was the most surgical change we could make.

While it's possible to re-enable this functionality on the client, it increases their attack surface. We're recommend talking to the game developer to see if they can eliminate the use of shared ByteArrays.

You can find additional details in this blog post:

Spectre / Meltdown Mitigations

D

dews

Inspiring

Why isn't there mention of this in the Release Notes?? This is a HUGE change for those of us actually using this - the fact that I had to be told of this by a client absolutely sucks.

PARTICULARLY because we were under the impression that we're "in the know" by reading the release notes! Come on.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded