Jest extension pegs cpu at 100% in latest VSCode insiders build

Environment

1. node -v: v8.4.0

2. npm -v: 4.6.1

3. npm ls jest or npm ls react-scripts (if you haven’t ejected): jest@23.1.0

4. your vscode-jest settings if customized:

   • jest.pathToJest? [fill]
   • jest.pathToConfig? [fill]
   • anything else that you think might be relevant? [fill]

5. Operating system: macOS 10.13.6

Prerequisite

• are you able to run jest test from command line? yes
• how do yo run your tests from command line? (for example: npm run test or node_modules/.bin/jest) npm run test -- --watch

Steps to Reproduce

I can’t do this as it’s proprietary code. However, everything was working fine until the latest VSCode insiders build at which Jest started pegging extensionHost at 100% cpu. I also filed https://github.com/Microsoft/vscode/issues/56951 since it’s not clear if the issue is with vscode-jest or vscode.

But prior to updating vscode, there was no issue and both jest and vscode flew along and did not peg cpu at 100%.

I’m on VSCode Insiders:

Version 1.27.0-insider (1.27.0-insider)
07796186d388044595cd101c49378c7cd48b350b
2018-08-21T08:33:22.481Z

Relevant Debug Info

[fill]

Expected Behavior

[fill]

Actual Behavior

[fill]

---

The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR…

[Jonafran]

I am running it on Version 2.9.1. and would like connect to @joelgetaction question - is there a posibility we can run traces to provide you more information?

Within < 5 seconds if I enable Jest Extension in vscode, all node.js threads wich are started by vscode have a load ~ 15% CPU usage and that makes in summary 100% CPU usage, wich is also been heard by my ears because the accelerators make a sprint to cool the system down.

My repo is a very large on and figuring out in what kind of jest line this issue appears would be a struggle. So traces could might help.

[connectdotz]

For people who suspect performance issues with this extension, you can help us narrow down the root cause by following vscode’s instruction to report a performance issue. Please do make sure to attch the profile output, something like xxx.cpuprofile.txt, in the issue.

Thanks.