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 introduced by Google Maps #138

Open
olegstepura opened this issue Mar 8, 2019 · 1 comment
Open

Memory leak introduced by Google Maps #138

olegstepura opened this issue Mar 8, 2019 · 1 comment

Comments

@olegstepura
Copy link

Hi!
We've been using ember-g-map for some time.
But we faced an issue possibly with google maps and I wonder if you are aware of it and maybe have some thought on fixing it.

I'm talking about memory leaks which Google Maps produce because there is no proper cleaning after we remove a map from page.
Here is an issue reported to google years ago https://issuetracker.google.com/issues/35821412
And it has status Won't fix. The only answer on how to solve that in that thread is recommendation to reuse (map canvas?) somehow.

We face an issue when we use Google Directions service and render polylines that it returns. If we create a complex path (like imagine DRIVING polyline around the whole USA) and close and reopen such map several times we get a huge memory leak. It's about 100Mb per opening of map which is not released then (manually triggerring GC in google chrome does not help).

Are you aware of such issues? Do you have any ideas on how to better reuse maps with this addon?

@ianpetzer
Copy link

Hi @olegstepura,

I saw in sandydoo/ember-google-maps#51 that you said you have a solution for this problem that works with ember-g-map. Is this maybe in a forked repo or a public repo so that I could re-use the same solution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants