From issues-return-791-apmail-flex-issues-archive=flex.apache.org@flex.apache.org Mon Sep 2 21:47:52 2013 Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1122310C5D for ; Mon, 2 Sep 2013 21:47:52 +0000 (UTC) Received: (qmail 97359 invoked by uid 500); 2 Sep 2013 21:47:52 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 97342 invoked by uid 500); 2 Sep 2013 21:47:52 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 97329 invoked by uid 99); 2 Sep 2013 21:47:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Sep 2013 21:47:51 +0000 Date: Mon, 2 Sep 2013 21:47:51 +0000 (UTC) From: "Justin Mclean (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLEX-19514) Error #1502 (Script timeout) in PriorityQueue and browser hangs when UI gets created with small XML result MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-19514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756251#comment-13756251 ] Justin Mclean commented on FLEX-19514: -------------------------------------- Have you tried a later version(s) of the SDK? The source to Adobe Flex 3 SDK was not donated to Apache so we are unable to change it. Someone however may know of a work around to this issue. > 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