Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1764704016.1256807819643.JavaMail.jira@brutus>
Date: Thu, 29 Oct 2009 09:16:59 +0000 (UTC)
From: "Felix Meschberger (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-1503) Component Factory instances are not
 let gone after dispose
In-Reply-To: <662182155.1250689094839.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Felix Meschberger resolved FELIX-1503.
--------------------------------------

    Resolution: Fixed

This issue has actually been resolved.

> Component Factory instances are not let gone after dispose
> ----------------------------------------------------------
>
>                 Key: FELIX-1503
>                 URL: https://issues.apache.org/jira/browse/FELIX-1503
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-1.0.6, scr-1.0.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.2.0
>
>
> Component factory instances retrieved with ComponentFactory.newInstance(Dictionary) are not removed from the internal maintenance data structure. In the longer run, this prevents the components from being garbage collected and eat up all memory.
> At one time we had a situation of 700'000 disposed ImmediateComponentManager instances kept in the ComponentFactory internal map....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.