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

Bug: Vs Code 开发时,经常报 “正在加载 IntelliSense 状态” ,同时CPU飚高且失去类型推断和代码提示 #4802

Open
5 tasks done
eamd-wq opened this issue Nov 4, 2024 · 5 comments
Labels
help wanted Extra attention is needed

Comments

@eamd-wq
Copy link
Contributor

eamd-wq commented Nov 4, 2024

Version

Vben Admin V5

Describe the bug?

排查了很久,可能是eslint规则的问题,但是最终还是没有找到具体原因;
打开项目开始写代码,刚开始正常,一段时间后:
image

同时编辑器非常卡顿,Vs Code的进程监视器也只能看到是项目占据了一定的CPU,正在检查我刚刚编辑的文件,并没有其他额外的提示;
此状态大约持续2-5分钟后会恢复正常

Reproduction

没有改动任何重要配置

System Info

Windows 11 ; Vs Code 1.95.1; Eslint插件v3.0.10; Vue - Official v2.1.10

Relevant log output

No response

Validations

@anncwb
Copy link
Collaborator

anncwb commented Nov 4, 2024

这个因素很多,可能是你的插件导致,也可能是配置问题。暂时没法复现,可以帮忙排查看看

@anncwb anncwb added help wanted Extra attention is needed and removed bug: pending triage labels Nov 4, 2024
@wangjue666
Copy link
Collaborator

@eamd-wq 可以把vscode的插件都先暂时停用,然后把 .vscode/extensions.json 这个文件中的插件都启用,试试看

@eamd-wq
Copy link
Contributor Author

eamd-wq commented Nov 6, 2024

@eamd-wq 可以把vscode的插件都先暂时停用,然后把 .vscode/extensions.json 这个文件中的插件都启用,试试看

好的,我先照做试一段时间,如果再有复现我再来寻求帮助;感谢
我觉得应该不会只有我遇到这个问题,所以我一定要解决它

@eamd-wq
Copy link
Contributor Author

eamd-wq commented Nov 10, 2024

@eamd-wq 可以把vscode的插件都先暂时停用,然后把 .vscode/extensions.json 这个文件中的插件都启用,试试看

只能说有所改善,cpu还是会偶尔高,但是体感上没有之前那么严重;

现在会看到这个提示:ESLint-Validation took 12200ms
所以问题好像依然存在;我打算在空闲时重置我VS Code的云配置和本地配置,然后再使用一段时间再看看;

如有其他道友遇到同样问题,还请赐教

@eamd-wq
Copy link
Contributor Author

eamd-wq commented Nov 10, 2024

备注:我的CPU是 intel i7 11代

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants