Fix leaking listeners and DOM elements. #264
Closed
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Hey.
This is a brute force fix for leaking listeners and DOM elements. Currently scope parameter of link function is being passed via closure to listener function and to functions in data factory. As always in closures, this means that browser will keep whole context of the linking function, so here it will include element as well. It made proper garbage collection not possible (profiled on Chrome).
It can be fixed cleaner e.g. by using local variables in linking function and then passing those via closure or by restructuring the code a bit. Please excuse that I did not do it in the first place, but I do not know the project and had to quickly plug in this component.
I am pushing this PR just to provide a quick fix - in case anybody else would like to get rid of performance issues. If you decide to solve the problem in another way, please just ignore this PR.
Cheers!
Bartek