Prevent memory leaks in rivets adapters fix #10 #12
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.
Using
.bind(this)
onObserver#update()
create a new function instance each time: thereby, adapters can’t unobserve sightglass update callback.The solution is to keep an reference to the binded update method.
A pull request (#11) has allready been proposed by @jccazeaux, but:
var self
is unproperly initialised in the constructor, not in the methods that use it. And... anyway, even withself
properly initialised, usingself.update
remains a mistake (self.update remain a function, not an instance method).bind()
instead ofvar self
, because browsers support is large enough (and polyfilling bind() is easy)Fix #10 and mikeric/rivets#430