High CPU usage and high read IO usage

[ChiHoc]

Info

• Platform: OSX 10.12.5
• Vetur version: 0.9.1
• VSCode version: 1.14.2

Problem

I got a high cpu usage and high read IO usage vetur process.

process

high read IO usage

high cpu usage

Reproducible Case

1. Open a vue project. (224M, 24,110 files)
2. Use "workbench.action.files.showOpenedFileInNewWindow" key and open a new window.
3. Watch "Activity Monitor"

[gh67uyyghj]

#216

[octref]

#216 (comment)
https://vuejs.github.io/vetur/setup.html

[ChiHoc]

It works and feel sorry to open a duplicate issue. Thank you. @eronaeon @octref

[ChiHoc]

Um, it still seems happening when I open file in new window, even if exclude "dist" and include "src". ("src" is my vue project source dir)

[octref]

Does that happen with Vetur disabled?

[ChiHoc]

It works well with Vetur disabled.

[ChiHoc]

The key point that I open file in a new window, not a new tab.

[octref]

If there is no repro case I can't help you.

Does Vetur work well for other projects like egoist/vuepack or the webpack template?
Can you try to modify them to cause this error? Or is the error just because of you having too much files in your workspace?

[ChiHoc]

Here is the repro case.

Clone this demo project: https://github.com/bailicangdu/vue2-happyfri. ( 6.6 MB, 72 files)

Add jsconfig.json.

Open project in VSCode, and open a new window.

[octref]

I don't think it has anything to do with "Opening New Window". The problem is you are opening single vue file using a VSCode instance / window, without a workspace.

People have reported this issue before. Vetur cannot determine your tsconfig without a workspace.
Now we recommend always work on Vue project by opening the whole project as a workspace. But with the upcoming VSCode support for Multi-Folder workspace, I plan to look deeper into workspace and have better support for the two scenarios:

• opening single vue file
• opening multiple vue projects using Multi-Folder workspace