Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory leak since the EventListeners are not detached #437

Open
michaelarnauts opened this issue Jan 22, 2019 · 1 comment
Open

Memory leak since the EventListeners are not detached #437

michaelarnauts opened this issue Jan 22, 2019 · 1 comment
Assignees
Labels

Comments

@michaelarnauts
Copy link

michaelarnauts commented Jan 22, 2019

Describe the bug
It seems that various EventListeners on the document are added (PointerMove etc), but they are not detached when destroying the component.

To Reproduce
Steps to reproduce the behavior:

  • Setup a angular project with multiple pages and add a console.log in the onAfterViewChecked of the app component.
  • Add a map to one page.
  • Observe the console to see when change detection is triggered.
  • Navigate away to the blank page, and notice that a lot of change detections are still happening.

Expected behavior
This component should detach all EventListeners when destroying.

Environment (please complete the following information):

  • Base: Angular
  • Version 7
@atd-schubert
Copy link
Member

Thanks for the detailed description. I will take a look at it the next days...

@atd-schubert atd-schubert self-assigned this Jan 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants