You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if I don't run the project, but my IDE is just open,- my CPU usage is loaded by 80-90% from the beginning. And onQueryStarted handler causes this. Because when I comment this handler out, - CPU usage immediately gets loaded by few %.
I'm sorry, but this just sounds like the wildest thing. I fear it might not be something we can help you with, as that problem can be anything from a specific TypeScript version to a specific version of your IDE, or just any plugin you have installed there.
If you can reproduce that with a fresh project and a plain install of VSCode without extra plugins, I would be very interested to see a reproduction of this - but I fear that without that we can't really do anything about it.
Found out that this default plugin caused the issue (php storm IDE):
Even after when I turned it ON again, - everything is fine. Reloading IDE before didn't help, but this plugin does. Code works fine, no problems with CPU. Hope to never reproduce this in future=)
I can only recommend you try to use VSCode instead. WebStorm doesn't use the official TypeScript Type server, but some crutch they invented themselves they claim is "faster". That might fail in so many unexpected ways we cannot support - I'm sorry.
I'm learning RTK query with Redux-toolkit. Reading this article from docs:
https://redux.js.org/tutorials/essentials/part-8-rtk-query-advanced#implementing-optimistic-updates
I wrote exactly the same blog from documentation, but got a big issue with CPU.
Even if I don't run the project, but my IDE is just open,- my CPU usage is loaded by 80-90% from the beginning. And onQueryStarted handler causes this. Because when I comment this handler out, - CPU usage immediately gets loaded by few %.
Screen Recording 2023-04-12 at 20.01.59.mov.zip
The text was updated successfully, but these errors were encountered: