incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tigran Najaryan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-33236) Calling automationManager2.getChildren() on Spark DataGrid causes memory leak
Date Sat, 27 Oct 2012 11:47:14 GMT

     [ https://issues.apache.org/jira/browse/FLEX-33236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tigran Najaryan updated FLEX-33236:
-----------------------------------

    Description: 
To reproduce:

1. Import attached project to Flash Builder and run in Profile mode. 
2. Let the application load in browser and click "getAutomationChildrenArray" button. 
3. Watch how on every attempt to get children the total memory shown in flash Builder Profiler
view grows and never goes down.

The problem can be also seen clearly without profiler. Just watch "iexplore.exe" process memory
consumption in Task Manager.

The problem only occurs if there are item renderers that are not visible.

Possibly caused by GridColumnHeaderGroupLayout/getHeaderRendererAt() creating item renderer
at line 597 via call to allocateVisualElement and never releasing it.

  was:
To reproduce:

1. Import attached project to Flash Builder and run in Profile mode. 
2. Let the application load in browser and click "getAutomationChildrenArray" button. 
3. Watch how on every attempt to get children the total memory shown in flash Builder Profiler
view grows and never goes down.

The problem can be also seen clearly without profiler. Just watch "iexplore.exe" process memory
consumption in Task Manager.

Possibly caused by GridColumnHeaderGroupLayout/getHeaderRendererAt() creating item renderer
at line 597 via call to allocateVisualElement and never releasing it.

    
> Calling automationManager2.getChildren() on Spark DataGrid causes memory leak
> -----------------------------------------------------------------------------
>
>                 Key: FLEX-33236
>                 URL: https://issues.apache.org/jira/browse/FLEX-33236
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: AgentAPI, Spark: DataGrid
>    Affects Versions: Adobe Flex SDK 4.6 (Release)
>         Environment: Windows 7, Flash Builder 4.x, Internet Explorer 9
>            Reporter: Tigran Najaryan
>              Labels: automation
>         Attachments: MemoryLeakTest.fxp
>
>
> To reproduce:
> 1. Import attached project to Flash Builder and run in Profile mode. 
> 2. Let the application load in browser and click "getAutomationChildrenArray" button.

> 3. Watch how on every attempt to get children the total memory shown in flash Builder
Profiler view grows and never goes down.
> The problem can be also seen clearly without profiler. Just watch "iexplore.exe" process
memory consumption in Task Manager.
> The problem only occurs if there are item renderers that are not visible.
> Possibly caused by GridColumnHeaderGroupLayout/getHeaderRendererAt() creating item renderer
at line 597 via call to allocateVisualElement and never releasing it.

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