Angularjs Node Leaks

[samccone]

Steps to reproduce

• start timeline profiler
  • add three todos
  • delete three todos
  • (repeat above 2 more times)
• force GC
• stop timeline profiler

---

Looks like we are leaking DOM nodes ⛲

[samccone]

ping @IgorMinar

[sindresorhus]

@btford Do you know anyone on the Angular team able to look at this?

[btford]

Idk if this definitively proves a memory leak. @samccone – if you repeat these steps, does memory continue (unbounded) to grow?

What version of Angular do you see this? And do you see this behavior in browsers besides Chrome?

It's probably good to cross-file this on angular/angular.js, but I'll ping the team and see if anyone can take a look.

Thanks!

[samccone]

Hey @btford Let me update these numbers with the most recent results 👍

[arthurvr]

It's probably good to cross-file this on angular/angular.js, but I'll ping the team and see if anyone can take a look.

Thanks. Has someone been able to look into this yet? :)

[flashdesignory]

Closing, since the Angular example was updated #2212