Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Memory leak when computing displayObject's transformMatrix #106

Closed
Fraggle opened this issue May 7, 2012 · 2 comments
Closed

Memory leak when computing displayObject's transformMatrix #106

Fraggle opened this issue May 7, 2012 · 2 comments

Comments

@Fraggle
Copy link

Fraggle commented May 7, 2012

Hi,

While working on our game, we noticed some issue with object still in memory that shouldn't.
After a bit of profiling, we found the culprit:

In getTransformationMatrix of DisplayObject, you are using sAncestors Vector to hold the hierarchy of parents, but you are not emptying it afterwards. So all the hierarchy is still referenced from that object after the method complete.

I suggest setting the length to 0 line 220 and line 250.

Sebastien
@PrimaryFeather
Copy link
Contributor

Thanks for the report! Fixed just in time for Starling 1.1 ;-)

@Fraggle
Copy link
Author

Fraggle commented May 7, 2012

No problem :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Fraggle @PrimaryFeather