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

state, render, currentRoute errors in console #2146

Open
Parsa361 opened this issue Mar 9, 2024 · 3 comments
Open

state, render, currentRoute errors in console #2146

Parsa361 opened this issue Mar 9, 2024 · 3 comments

Comments

@Parsa361
Copy link

Parsa361 commented Mar 9, 2024

Vue devtools version

6.6.1

Link to minimal reproduction

None

Steps to reproduce & screenshots

Sometimes these errors will be printed in the console and I don't know what exactly makes it happen but I think when I'm using the select tool It happens
image

What is expected?

No error printed in the console

What is actually happening?

About 2000 errors were printed in the console

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (4) x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Memory: 11.06 GB / 19.88 GB
  Binaries:
    Node: 14.21.3 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.18 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (122.0.2365.66)
    Internet Explorer: 11.0.19041.3636
  npmPackages:
    vue: ^2.6.11 => 2.7.14

Any additional comments?

No response

@evb0110
Copy link

evb0110 commented Mar 14, 2024

Same errors in our project

@sqlnice
Copy link

sqlnice commented Mar 15, 2024

Our project uses "@vue/composition-api": "^1.0.0-rc.8 ", "vue": "~2.6.10 ", this error has occurred for 2 years, each time can only refresh the tab and close and open the F12 console again, otherwise the tab memory will overflow。

@ali2966
Copy link

ali2966 commented Apr 3, 2024

i'm facing the same issue, it's really annoying.

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

4 participants