Does addEventListener cause memory leaks?

Question

I'm writing an angular app, and I'm using addEventListener for several events. My question is, when the route changes, are the event listeners still active? And if so do they need to be manually removed to prevent memory leaks?

I'm targeting modern browsers: Safari, Firefox, Chrome, IE >= 10

Why are you using `addEventListener` in an Angular app when it already has so many event methods available to it? — Josh Burgess, Aug 14 '15 at 20:10
I don't really have an answer for that. I have a weird habit of trying to use vanilla js whenever its available. So to that end, does .on need to be unbound on DOM changes? — richbai90, Aug 14 '15 at 20:14

score 0 · Accepted Answer · edited May 23 '17 at 12:32

0

When using 'vanilla js' to bind events to the dom they will not be unbound, so you should manually do this. I see no reason why you would bind events like this when using angular though.

A nice post explaining everything: https://stackoverflow.com/a/27016855/5223929

edited May 23 '17 at 12:32

Community

1
1

answered Aug 14 '15 at 20:32

Wout De Rooms

647
4
10

Does addEventListener cause memory leaks?

1 Answers1