Skip to main content
S
Schuhster
New Participant
August 13, 2011
Question

10.3.183.5 bug with shared libraries and goto statements

  • August 13, 2011
  • 5 replies
  • 9992 views

We detected a severe bug in the latest flash player (10.3.183.5) running a customers commercial flash 6 application. This AS1 application uses shared libraries and loadMovie calls. It has been running for more than 100,000 users/year problem free since the release of flash player 6/7 until yesterday. The 10.3.183.5 flash player unloads all content at specific points resulting in a empty (black) screen. You can call it a crash. There seems to be bugs in the execution of gotoAndPlay() and gotoAndStop() and in the management routines of shared libraries because we could avoid the black screen crash by commenting out the goto handlers or unbinding linked items from shared libraries.

Our testing configruations:

Win XP, IE8, FF5
Win 7, IE9, FF5
Mac OS 10.6, FF5
Mac OS 10.7, FF5

Under Mac OS 10.7 there is a freezed screen instead of a black screen, but the player context menu tells us that there is no movie loaded like in Windows testing configuration.
In all environments the black screen doesn't occur on later player version than 10.3.183.5.

Please fix these bugs or give us informations about a workaround for the "black screen effect" in flash player 10.3.183.5 or rather a statement.

    This topic has been closed for replies.

    5 replies

    chris.campbell
    Community Manager
    chris.campbellCommunity Manager
    Community Manager
    August 25, 2011

    A new version of the player was released last night that should address this issue.  For additional details, please see the following post:

    Flash Player 10.3.183.7 Released

    Thanks,

    Chris

    P
    PPM
    Participating Frequently
    August 25, 2011

    Hi Chris,

    This certainly seems to have eliminated the issue!

    Thanks for your help and for keeping us updated.

    Can you explain how Adobe will ensure that this does not happen again?

    The RSS feed you mentioned above does not currently show that a new player has been released.

    If the feed is the only way to be notified of releases, how long should it take for the updated player to be in the RSS?

    Based on this one example, it would seem like our users are more likely to tell us that a new player is available than the RSS!

    Regards,

    Ian

    chris.campbell
    Community Manager
    chris.campbellCommunity Manager
    Community Manager
    August 25, 2011

    Hi Ian,

    While I can't promise that we won't have bugs in our future releases, we do treat injections (bugs added with the last release) as a top priority.  We'll be adding test cases (both manual and automated) for all of the bugs found in 10.3.183.5 and I'm sure we'll have a thorough post mortem to figure out what went wrong.

    I'm not sure why the runtime releases feed has not been updated, but I'm looking into it and I'll see if we can add this to our release checklist (if it isn't already).

    Thanks,
    Chris

    A
    astro_mike
    New Participant
    August 17, 2011

    Yes,, it would appear that this 10.3.183.5 update has broken the third-party Flash countdown timers on two of my websites:-

    http://www.levinstargazers.org.nz

    http://www.marssociety.org.nz

    As they are both Google sites, the third-party Flash component is "installed" by completing settings in the "Admin panel" at http://www.usflashmap.com/component/countdown_timer.htm and copying the HTML code that is generated.  Now the countdown timers just appear as a blank white rectangle on the page.  Right-clicking the rectangle opens the Flash context menu, which states "Movie not loaded".

    Unfortunately, after upgrading to this release, even the Admin panel referred to above is no longer visible (presumably this is a Flash component also).  After reading about some of the issues in this forum, I uninstalled this release and reinstalled 10.3.181.34, which has fixed the problem for me, but our website users that have already ugraded to the latest release will be affected by this issue.

    Our websites are far from "high volume", but I imagine that this will be impacting some others quite severely!

    J
    Javier_Y
    New Participant
    August 17, 2011

    Do not understand how Adobe has not stopped the distribution of version 10.3.183.5. Every day there aremore users with a version that makes it unusable for many applications. It seems a very serious situation.

    J
    Joe_Paice
    New Participant
    August 15, 2011

    We have encountered exacly the same issue. We also found that the nextFrame() function is affected.

    Our testing config:

    Win XP, IE7, FF5, Chrome

    We could avoid this by calling a method on the parent object that then calls nextFrame(), or other goto method.

    This is a critical issue for us so any updates would be much appreciated.

    I have logged a bug on bugbase but can not get the issue number due to security issues.

    S
    SchuhsterAuthor
    New Participant
    August 15, 2011

    Meanwhile we posted the issue to Adobe bugbase also.

    Unfortunately your workaround didn't solve this problem for our application. In some very few cases we could avoid the crash by reordering the movie timeline in order to make play head jump in positive direction instead of jumping back.

    Successfull tests with Flash Player 11 beta (32 Bit and 64 Bit) revealed, that this bug is only an issue for the 10.3.183.5 player.

    chris.campbell
    Community Manager
    chris.campbellCommunity Manager
    Community Manager
    August 17, 2011

    Chris,

    Thanks for looking into this problem, this for us is a "Show Stopping" terminal bug.

    It is not feasible to modify our application to remove all the code that triggers this bug, we have 10 years of development invested several thousand files in our product which has been made unusable by this "Security update".

    Adobe are recommending that everyone upgrade to this version knowing that this will cause flash to fail on all sites that use a shared library.  We've just had to issue and advisory to our customers to inform them that if they want to continue to use the software they are paying for that they have to stay on an older, known to be insecure, version of the player.

    Yes, the Player 11 Beta2 does work, it shows no sign of this issue for us, but when is this going to be released? (before the end of 2011?)

    What can I tell our customers?  When are they going to be able to both use our product and not be at risk from running an insecure player?

    Regards,

    Ian.


    Hi Ian,

    Thank for you the feedback.  I believe you've also commented on the bug, but if you haven't please do vote and leave a comment.

    I've passed all this feedback along to our team and we're actively looking into this with the highest priority.  As soon as I have additional details I'll share them here.

    Chris

    pwillener
    pwillener
    Brainiac
    August 13, 2011

    It would be best if you filed a bug report at http://bugbase.adobe.com/ and then post the bug number back in this topic.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices