flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLEX-35312) Memory Leak in GridViewLayout
Date Wed, 24 May 2017 20:28:04 GMT

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

Jason Taylor updated FLEX-35312:

the ClearCache method is there to provide a method for a user to explicity flush the renderer
cache, so it would only be called from user code.   For me most of my views implement a Destroy
method, and in my custom grid component it's Destroy method calls the clear cache internally.

> Memory Leak in GridViewLayout
> -----------------------------
>                 Key: FLEX-35312
>                 URL: https://issues.apache.org/jira/browse/FLEX-35312
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: Grid
>    Affects Versions: Apache Flex 4.13.0, Apache Flex 4.12.1, Apache Flex 4.14.0, Apache
Flex 4.15.0, Apache Flex 4.14.1, Apache Flex 4.16.0, Apache Flex 4.17.0
>         Environment: All
>            Reporter: Jason Taylor
>              Labels: memory, memory-leak, spark
>         Attachments: jtaylor_flexsdk_gridviewlayoutcache_patch.diff
> The Spark GridViewLayout uses strong dictionaries for caching itemrenderers, often leading
to a situation where those itemrenderers are never released to the garbage collector.
> The proposed patched changes GridViewLayout to use weak reference dictionaries and additionally
adds a public method to Grid to allow the client to explicitly flush the item renderer cache.

This message was sent by Atlassian JIRA

View raw message