flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Harui (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-19514) Error #1502 (Script timeout) in PriorityQueue and browser hangs when UI gets created with small XML result
Date Tue, 03 Sep 2013 04:11:52 GMT

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

Alex Harui commented on FLEX-19514:
-----------------------------------

This most often happens when a component cannot decide on its size or whether it should have
scrollbars or not.  Often, setting an explicit width or height on a component can help it
make up its mind.
                
> Error #1502 (Script timeout) in PriorityQueue and browser hangs when UI gets created
with small XML result
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: FLEX-19514
>                 URL: https://issues.apache.org/jira/browse/FLEX-19514
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Layout - General
>    Affects Versions: Adobe Flex SDK Previous
>         Environment: Affected OS(s): All OS Platforms
> Affected OS(s): All OS Platforms
> Language Found: English
>            Reporter: Adobe JIRA
>            Assignee: Adobe JIRA
>
> Steps to reproduce:
> Eh, bad title, but...
> 1. Import the attached project
> 2. Run/Debug
> 3. Click 'Login' button in Login Window (ok to leave fields empty)
>  
>  Actual Results:
> Browser hangs evern after I stop the debugger, and:
>  Error: Error #1502: A script has executed for longer than the default timeout period
of 15 seconds.
> 	at mx.managers.layoutClasses::PriorityQueue/removeLargestChild()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\layoutClasses\PriorityQueue.as:175]
> 	at mx.managers::LayoutManager/validateClient()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\LayoutManager.as:911]
> 	at mx.core::UIComponent/validateNow()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\UIComponent.as:6881]
> 	at mx.core::UIComponent/creationCompleteHandler()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\UIComponent.as:10436]
> 	at flash.events::EventDispatcher/dispatchEventFunction()
> 	at flash.events::EventDispatcher/dispatchEvent()
> 	at mx.core::UIComponent/dispatchEvent()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\UIComponent.as:11260]
> 	at mx.core::UIComponent/set initialized()[E:\dev\beta1\frameworks\projects\framework\src\mx\core\UIComponent.as:1513]
> 	at mx.managers::LayoutManager/doPhasedInstantiation()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\LayoutManager.as:759]
> 	at mx.managers::LayoutManager/doPhasedInstantiationCallback()[E:\dev\beta1\frameworks\projects\framework\src\mx\managers\LayoutManager.as:1067]
>  
>  Expected Results:
>  This is dealing with a small xml result: 
> http://twitter.com/statuses/public_timeline.xml
> it definitely shouldn't be timing out. The code that handles this result is in PublicTimelineProxy
>  
>  Workaround (if any):

--
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

Mime
View raw message