Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I actually found my issue with this. I had an object in my vuex store that was large (an array with ~ 1,000 elements). Each element was just s simple object with around 10 properties). As soon as I truncated this array to only contain 100 elements everything worked perfectly again. So it's a performance issue with a large array in the store when dev tools is open. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm not sure the best place to put this question - I don't think it's a bug, but I'm hoping to get some assistance.
Recently performance has degraded to the point where I can't use the tools. I'm using the Chrome extension (v 6.4.4) on Windows. I know that I should be creating a performance profile for you to best analyze this so I went through all of the steps to create it (super easy by the way - nice documentation), but when I run my app locally the vue devtools just freeze and never open, so my performance is not impacted at all. For that reason, I'm unable to provide a performance profile that contains the issue.
I've tried all of the normal tips of disabling performance monitoring, keeping 'update tracking' disabled, etc. but with no luck.
This is a big project and hard for me to make available as a repro (although I will explore trying to do it if needed). I do see 2 warnings in my console after I turn 'Debugging Info' on in the global settings. These errors are:
Inspector vue2-vuex-inspector not found
Timeline layer vue2-vuex-mutations not found
Does anybody have any thoughts on what these 2 warnings might be from and how to resolve them?
I believe this issue is related to something with vuex (I'm using vuex 3.4.0 & vue 2.6.11).
Thanks for any help or direction you can give.
Beta Was this translation helpful? Give feedback.
All reactions