Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Cleanup cross context memory on dispose #37

Open
kpdecker opened this issue Jul 8, 2014 · 1 comment
Open

Cleanup cross context memory on dispose #37

kpdecker opened this issue Jul 8, 2014 · 1 comment
Labels
bug
Milestone
1.0.0

Comments

@kpdecker
Copy link
Contributor

kpdecker commented Jul 8, 2014

The memory retain behavior that we've seen when creating multiple contexts can likely be resolved by manually cleaning all cross-context connections, per TJ.

We need to go to vet that we are cleaning these all of these references as part of the dispose operations.
@kpdecker kpdecker added the bug label Jul 8, 2014
kpdecker added a commit that referenced this issue Jul 10, 2014
@kpdecker
Explicitly break cross context DOM links
4dca494 
Partial fix for #37
kpdecker added a commit that referenced this issue Jul 10, 2014
@kpdecker
Add dispose logic for jQuery objects
d4e4fcf 
Partial fix for #37
kpdecker added a commit that referenced this issue Aug 6, 2014
@kpdecker
Further isolate client from fruit loops code
e0cb0bd 
- Creates bootstrap code for data that doesn’t need to be run in the fruit loops context
- Adds dispose logic for the root location property accessor
- Moves client APIs into FruitLoops objects

Partial fix for #37
Fixes #36
@kpdecker
Copy link
Contributor Author

brianmcd/contextify#124 and related issues are most likely the primary cause of this. We should reevaluate this after that has made it into a release channel (or is deemed to be the incorrect fix)

@kpdecker kpdecker modified the milestone: 1.0.0 Feb 13, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@kpdecker