You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Alex Harui (JIRA)" <ji...@apache.org> on 2013/04/01 15:37:15 UTC

[jira] [Commented] (FLEX-33469) URL LOADER doesn't load images completely for count more than 200

    [ https://issues.apache.org/jira/browse/FLEX-33469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618776#comment-13618776 ] 

Alex Harui commented on FLEX-33469:
-----------------------------------

The main portion of the test case is not using Flex, just low level Flash APIs.  Please try creating a non-Flex, ActionScript-only test project and see if the limitation is from the runtime itself.  If it is, you will have to work with Adobe support.

I think there is an upper limit on number of open requests, so you may need to build a subsystem that queues requests, opens some smaller number and waits for them to finish before opening more.
                
> URL LOADER doesn't load images completely for count more than 200
> -----------------------------------------------------------------
>
>                 Key: FLEX-33469
>                 URL: https://issues.apache.org/jira/browse/FLEX-33469
>             Project: Apache Flex
>          Issue Type: Bug
>    Affects Versions: Adobe Flex SDK 4.6 (Release), Apache Flex 4.8 (parity release)
>         Environment: FLEX SDK 4.6
>            Reporter: Abhishek Dwevedi
>         Attachments: sample1_adobe.mxml
>
>
> Loader does not send OPEN/COMPLETE event when loading many times. , When loading any image for 500, the total of response should be the same with the request times set , but its NOT.
> Please find the attachment sample, case and follow steps to replicate
> *Run Sample1 or sample2, input an available image url in the [URL].
> *Input times you want to load in "Run times" and then click "execute load".
> * Check the "complete + io error count:" area

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira