Memory leak when unbinding document events #428
Merged
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.
When unbinding the document click event, the call is incorrect, leaving the document event attached, creating a memory leak that can quickly clog the memory when instantiating / destroying many instances of the datepicker.
This PR fixes that issue.
In order to showcase it, see this JSFiddle. If you open the Performance profiler in Chrome and track memory allocation (make sure to force garbage collection before stopping the profiling), after running the JSFiddle you'll see this:
Which is an obvious HTML node memory leak.
You can check this JSFiddle to see this fix in action. After doing the same profiling process, we get this: