Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F2694200C7F for ; Wed, 24 May 2017 22:28:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F0DB3160BD0; Wed, 24 May 2017 20:28:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 43AF0160BA5 for ; Wed, 24 May 2017 22:28:08 +0200 (CEST) Received: (qmail 29844 invoked by uid 500); 24 May 2017 20:28:07 -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 29835 invoked by uid 99); 24 May 2017 20:28:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2017 20:28:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C6EFE190DC2 for ; Wed, 24 May 2017 20:28:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id YP5Ne8AjcAiT for ; Wed, 24 May 2017 20:28:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id A223B5FD90 for ; Wed, 24 May 2017 20:28:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 3DCE7E0D50 for ; Wed, 24 May 2017 20:28:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5DFED21B5B for ; Wed, 24 May 2017 20:28:04 +0000 (UTC) Date: Wed, 24 May 2017 20:28:04 +0000 (UTC) From: "Jason Taylor (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLEX-35312) Memory Leak in GridViewLayout MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 24 May 2017 20:28:09 -0000 [ 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 (v6.3.15#6346)