Flash Player 10.1.53.64 hangs during initialization

Question

(Forking off from [previous issue created by me|Flash Player 10.1; that was since stickied and dedicated to a PowerPoint issue.)
SWFs generated on a machine where Flash Player 9.0.115.0 is installed, and viewed in any web browser on machines with FP 10.1.53.64, hang indefinitely during the initialization sequence.
As noted in the previous thread, SAP has submitted an issue to Adobe (that could be similar or related) here:
https://bugs.adobe.com/jira/browse/FP-4843
Noting that Adobe has addressed the above issue, does this fix extend to web browser plugin versions of the Flash Player as well?

Answer 1

Hi Matt,
i am also interested in the conditions in which the bug arises. I developed an complex application using Xcelsius 5.3.1.0 with
Flash 10.1.82.76 installed on the development machine on Windows XP SP 3. At a certain point of the development
it was not possible anymore to preview application in the development environment. After generating the SWF the
development environment crashed while initializing the application. But the generation of the SWF file was successfull and
also can be done without errors using the export function.
To solve the issue with the current adobe flash player i downloaded the adobe flash projector of the older version 10r42_34,
loaded the generated SWF without any problems (on the development machine) and used the function "create projector" to create
a stanalone application that includes the player.
The ".EXE" generated worked fine on the development maschine as well as on a couple of other machines. With the corresponding projector for Mac OS we also generated an application including the player for OS X wich also works fine on
some mac books.
On the other hand, the application hang in the initialization process on other windows machines without showing any rule
by hardware or software configuration (see also the Post from Francis86 in Thread "Hanging during utilization: Flash Player 10.1.53.64").
Two other aspects might be of interest for you:
1) In the context of the development i also experienced problems after a certain amount of components had been added, resulting
in a crash of the development environment. The only way to solve the problem was to delete components or replace them by others. It would be interesting to know where the limitations are.
2) The tab-component seems to produce additional problems. The first design of the application structures the application in different views utilizing a tab component with 5 tabs and a lot of components (as few as possible) on each tab. The problem arose if one uses the reset-button component. The reset did not work for every component within the different tabs. By random some of the initial values had been reseted to its original state, others had be set simply to 0 ignoring its initial state.
I could only solve this problem by replacing the tab component with a menu and using visibility rules. This results in solver responsibility when switching betweent the "tabs" but the reset works fine afterwords.