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

large CPU and Memory usage on open Vue devtool window #404

Open
1 task
nailfor opened this issue Jun 13, 2019 · 2 comments
Open
1 task

large CPU and Memory usage on open Vue devtool window #404

nailfor opened this issue Jun 13, 2019 · 2 comments
Labels
confirmed Issue is accepted as either a bug or a valid enhancement help wanted

Comments

@nailfor
Copy link
Contributor

nailfor commented Jun 13, 2019

My application uses a web socket to update markers and show transport .
When I open devtool, I see a huge amount of events [ready $emit by LGeoJson]
Chrome uses 2GB, the CPU goes to a zone above 60%
On my map about 20 static LGeoJson and 100 static event markers are displayed.
Even with such a small number of objects, I get crash vue devtool.

If I go to tab "Events" and push "clear" events, the memory is released, there is no load CPU and no crush devtool.

Next, I add transport objects whose coordinates change dynamically on a web socket and see events [update: latLng $emit by LMarker]
There are a lot of them and it is very difficult to track down the desired event.

I understand that the problem is most likely in dev tools, but is it possible to disable map objects from $emit?

Browsers Affected

  • Chrome 75.0.3770.80
    vue devtool 5.1.0

Versions

Leaflet: v1.5.1
Vue: v2.6.7
Vue2Leaflet: v2.1.1
@DonNicoJs
Copy link
Member

At the moment we have no way to disable the events, and yes it's a vue dev tool issue that occur in other cases as well.

Would you consider a PR to add a kill switch for events?

@stale
Copy link

stale bot commented Jan 1, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 1, 2020
@DonNicoJs DonNicoJs added confirmed Issue is accepted as either a bug or a valid enhancement and removed wontfix labels Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
confirmed Issue is accepted as either a bug or a valid enhancement help wanted
Projects
None yet
Development

No branches or pull requests

2 participants