[TIMOB-16194] Alloy: Memory leaking if animation call callback
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Open |
| Resolution | Unresolved |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | alloy, animation, callback, leak |
| Reporter | Matej |
| Assignee | Unknown |
| Created | 2013-12-31T02:28:55.000+0000 |
| Updated | 2018-02-28T20:04:20.000+0000 |
Description
Application is leaking if animation call callback function. If is animation without callback everything is alright...
I have putted to the archive whole project including video from the app & instruments.
(If is possible please reupload it on some better place / pick up only important informations. Archive can be deleted in the future)
http://www.filedropper.com/memleak
Please can somebody have a look on this issue? Thanks
Matej, Yes, this will be moved to TIMOB for engineering review. Thanks, Shak
I'm running in to this issue but in the case of this code sample, I don't see where things are supposed to go out of memory. The view is always referencable so it wouldn't go out of memory anyway. A good test is using the Alloy animation builtin - it has the leak since it uses the callback instead of the animation complete event. https://github.com/appcelerator/alloy/blob/master/Alloy/builtins/animation.js - if when the view you're animating goes out of scope and there's no reference left in JS, it will be retained along with anything where the callback falls in to scope (it is a closure after all). i.e. Nulling out the callback and the view, etc. won't release it.
Hi Rick, have you seen attached video? Number of used views is increasing without any release... // Yes the problem is in a callback ,but without Alloy it works properly.