-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
It is suspected that vue-devtools causes chrome memory overflow and then crashes #2167
Comments
I am facing the same issue, and Chrome has become slow as a result. After uninstalling devtools, Chrome returned to normal. |
Same here vue-devtools became unusable. Constant freeze, such a pain |
how did you roll back to 6.5.1? Unfortunately, 6.6.1 is too buggy to use |
How install 6.5.1 version? |
|
I'm having this problem in Chrome, Edge, and Firefox for Linux. |
Same issues on MacOS edge and chrome for me. Happens most of the time when switching between components, vuex, routes, and timeline tabs. |
i have the same problem |
Two months have passed, yet the issue remains unresolved. |
I also encountered this issue where devtools caused 100% CPU usage. Vue devtools gives me a feeling of being abandoned. Everyone can try using another beta version,He's on the homepage. link is https://github.com/vuejs/devtools-next |
same issue, chrome on linux and mac showing cpu spike usage and eating memory faster than i can quit the browser. |
same, becomes unusable within a minute or two, can see the memory usage just going crazy over 3 gb for the window with vue Dev tools open! cpu 25%, memory going thru roof :( |
Vue devtools version
v6.6.1
Link to minimal reproduction
Steps to reproduce & screenshots
Step to reproduce:
Then my chrome crashed.
What is expected?
vue-tools shouldn't crash chrome
What is actually happening?
Using vue-devtools in the chrome browser will cause chrome to crash. And other developers around me also have the same problem.
System Info
Any additional comments?
This problem will occur in both vue2 and vue3.
Now I have rolled back the version to v6.5.1 and it is working.
The text was updated successfully, but these errors were encountered: