felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4247) Memory leak with ServiceUsage and inner class (Listener style)
Date Mon, 30 Sep 2013 09:48:27 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781715#comment-13781715
] 

Clement Escoffier commented on FELIX-4247:
------------------------------------------

To fix the leak we must introduce the same interception we do in component class. I'm going
to create a couple of subtasks required to fix it.

> Memory leak with ServiceUsage and inner class (Listener style)
> --------------------------------------------------------------
>
>                 Key: FELIX-4247
>                 URL: https://issues.apache.org/jira/browse/FELIX-4247
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-runtime-1.10.1
>            Reporter: Guillaume Sauthier
>             Fix For: ipojo-manipulator-1.10.2, ipojo-runtime-1.10.2
>
>
> Assume that you have a @Component using a swing-like technology with a load of Listeners
and callbacks.
> You'll probably write something like:
> {code:java}
> button.addClickListener(new ClickListener() {
>    // boilerplate code
>    myDependency.useIt();
> });
> {code}
> Where myDependency is a @Requires field.
> When the listener is executed, it is used from outside of the component (from iPOJO POV),
its method is not intercepted and a reference is kept in ServiceUsage$Usage.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message