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

High CPU Usage on macOS & dependency resolution failure #691

Closed
3 tasks done
ajmas opened this issue Feb 12, 2018 · 9 comments
Closed
3 tasks done

High CPU Usage on macOS & dependency resolution failure #691

ajmas opened this issue Feb 12, 2018 · 9 comments
Labels

Comments

@ajmas
Copy link

ajmas commented Feb 12, 2018

  • I have searched through existing issues
  • I have read through docs
  • I have read FAQ

Info

  • Platform: macOS 10.13.3 - MacBookAir6,2
  • Vetur version: 0.11.7
  • VS Code version: 1.20.0

Problem

From time to time I will encounter high CPU usage as soon I try to resolve a dependency (ctrl-click -> select 'go to definition') in a .vue file. The 'Code Helper' process will at that point be around 90% CPU until I kill the process or quit Visual Studio Code.

At the time this happens no code dependencies can be resolved. For example, the following type of import will sometimes resolve in the dependency not being found and being in a stuck:

import CrudView from '../../components/CrudView';

Reproducible Case

I haven't been able to establish a pattern, though would appreciate any suggestions that could help me identify which code might be causing the issue, which I could then share with you.

@octref octref added the perf label Feb 13, 2018
@octref
Copy link
Member

octref commented Feb 13, 2018

When I'm fixing #547 I'll put in some options to turn on logging. Currently there is no way to easily collect log so I can't offer much help yet.

@Tang-RoseChild
Copy link

same problem +1

4 similar comments
@zhaopengme
Copy link

same problem +1

@jamki
Copy link

jamki commented May 14, 2018

same problem +1

@vfasky
Copy link

vfasky commented May 16, 2018

same problem +1

@negope
Copy link

negope commented May 16, 2018

same problem +1

@octref
Copy link
Member

octref commented May 17, 2018

For people who were having CPU spike yesterday, 0.12.3 should fix it for you. The original poster's problem is a different one.

@ajmas Is your project open source or sharable with me?

@ajmas
Copy link
Author

ajmas commented May 17, 2018

I work on multiple projects, some of which are closed source. The one I remember having issues with was closed source. I haven’t spent too much time on that project recently, so I can’t say if the issue still presents itself.

@octref
Copy link
Member

octref commented May 17, 2018

@ajmas Thanks - if you do manage to narrow down to a repro case where this constantly happen, feel free to reopen the issue or open a new one.

@octref octref closed this as completed May 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants