You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Sandro Martini (JIRA)" <ji...@apache.org> on 2012/05/02 14:24:52 UTC

[jira] [Updated] (PIVOT-792) memory leak : window is still referenced after window.close() when using acitvity indicator or other timer-related callback components

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

Sandro Martini updated PIVOT-792:
---------------------------------

    Affects Version/s:     (was: 2.0.1)
        Fix Version/s:     (was: 2.0.2)
                       2.1
    
> memory leak : window is still referenced after window.close() when using acitvity indicator or other timer-related callback components
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIVOT-792
>                 URL: https://issues.apache.org/jira/browse/PIVOT-792
>             Project: Pivot
>          Issue Type: Bug
>    Affects Versions: 2.0
>         Environment: current pivot trunk
>            Reporter: Andrei Pozolotin
>            Priority: Minor
>             Fix For: 2.1
>
>
> memory leak : window is still referenced after window.close() when using acitvity indicator or other timer-related callback components
> here is bug project
> https://github.com/carrot-garden/carrot-bugger/tree/master/carrot-bug-pivot-memory-leak-000
> with 2 cases
> "NO LEAK"
> https://github.com/carrot-garden/carrot-bugger/tree/master/carrot-bug-pivot-memory-leak-000/src/main/java/com/carrotgarden/bug/case_1_no_leak
> "LEAK"
> https://github.com/carrot-garden/carrot-bugger/tree/master/carrot-bug-pivot-memory-leak-000/src/main/java/com/carrotgarden/bug/case_2_leak
> basically, if window uses activity indicator it is placed in timer queue and never removed on window.close();
> workaround: you must stop activity indicator manually via "on close" event listener;

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira