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.

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

DOM/Memory leaks. #5

Open
serviewcare opened this issue Jan 31, 2015 · 0 comments
Open

DOM/Memory leaks. #5

serviewcare opened this issue Jan 31, 2015 · 0 comments

Comments

@serviewcare
Copy link

Masonrify Seems to hold onto memory, and not appropriately destroy isotope elements underneath it.

Steps to Reproduce:
Use IronRouter, and visit a template using Masonrify.

Leave that route, and check out the Masonrify.instances variable in the console:

Masonrify.instances
Object {RecipientContainer: Masonrify, EmployeeContainer: Masonrify}

This is on a template that isn't showing any Masonrify elements. If you use Chrome memory profiling and inspect the heap for HTMLDivElements, you'll notice lots of detached (red) nodes that are all being retained by Masonrify at the root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

0 participants