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
Environment: current pivot trunk
Reporter: Andrei Pozolotin
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
