Error loading multiple swf in html

Question

Error loading multiple swf in html

Navigation

#1 by (1 votes)

2

I've created a report in ASP.NET and HTML which loads swf files into a for .

The problem is when the for is large and it needs to load several .swf files in the same report the flash simply does not run and gets marked with an exclamation (!) as you can see in the image below:

Hereisthecodeforhowtoloadtheswf:

<objectclassid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
        id="painelv3" width="100%" height="100%"
        codebase="http://fpdownload.macromedia.com/get/flashplayer/current/swflash.cab">
        <param name="movie" value="meuArquivoFlash.swf" />
        <param name="quality" value="high" />
        <param name="bgcolor" value="#ffffff" />
        <param name="allowScriptAccess" value="sameDomain" />
        <param name="FlashVars" value="<% =flashvar %>" />
        <embed src="<% =sUrl %>" quality="high" bgcolor="#ffffff"
            width="800" height="800" name="meuArquivoFlash" align="middle"
            play="true"
            loop="false"
            quality="high"
            allowScriptAccess="sameDomain"
            type="application/x-shockwave-flash"
            pluginspage="http://www.adobe.com/go/getflashplayer">
        </embed>
    </object>

html asp.net flash

asked by anonymous 19.12.2014 / 15:30

1 answer

Why define a constant for the same document and check if it exists in the document itself? What to do for this code to work on your phone

score 1 · Answer 1

This gray exclamation point, also known as GCOD , or Gray Circle of Death, appears when Flash Player is requesting more memory than the browser has available. If this alert did not exist, the browser would be terminated by the Operating System, due to lack of memory. It's a problem that needs to be addressed in your application, so I can only suggest solutions:

The Flash application could be optimized so that fewer resources were used, allowing you to load more instances on the same page.

If the Flash application uses many resources, but only at startup, it could communicate with the page through JavaScript and ExternalInterface , so that the next instance was started only after the previous one was completed.

In addition, instead of loading multiple instances of the same Flash application on the page, data could be passed to a single instance, which would display multiple items.

Other solutions can be implemented on the page without having to change the Flash-like paging-and some with the help of JavaScript-like enable only the instances that are visible on the screen, similar to pages that use videos and scrolling infinite.

The memory error warning was introduced in Flash Player 10.1 and more information can be accessed on the Official Adobe Blog: link