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

.NET Core Host CPU 100% #1117

Closed
deyanp opened this issue Jun 6, 2019 · 3 comments
Closed

.NET Core Host CPU 100% #1117

deyanp opened this issue Jun 6, 2019 · 3 comments

Comments

@deyanp
Copy link

deyanp commented Jun 6, 2019

Describe the bug
I am experiencing 100% CPU used by .NET Core Host under VS Code with very small F# projects consisting of 5-10 fs files

To Reproduce
Steps to reproduce the behaviour:

  1. Open VS Code with F# Project
  2. Work a bit (1-5 minutes)
  3. See 100% CPU usage in Windows Task Manager

Expected behaviour
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.
image

Environment (please complete the following information):

  • OS: Windows 10
  • Ionide version: 3.38.0
  • VSCode version: 1.35.0
  • dotnet SDK version: 2.2.300
  • mono / .Net Framework version:

Additional context
Add any other context about the problem here.

@open-collective-bot
Copy link

Hey @deyanp 👋,

Thank you for opening an issue. We will get back to you as
soon as we can. Also, check out our OpenCollective and consider
backing us.

https://opencollective.com/ionide

PS.: We offer backer support for all backers. Don't forget to add backer label when you start backing us 😄

@deyanp
Copy link
Author

deyanp commented Jun 6, 2019

these are the process' command line arguments, so it seems fsautocomplete.dll is working all the time on something?

"C:\Program Files\dotnet\dotnet.exe" C:\Users\Deyan.vscode\extensions\ionide.ionide-fsharp-3.38.0/bin_netcore/fsautocomplete.dll --mode http --port 8840 --hostPID=6424 20944

@deyanp
Copy link
Author

deyanp commented Jun 20, 2019

Just to note that after updating package references to FSharp.Core 4.6.2 the issue seems to be gone ...

@deyanp deyanp closed this as completed Jun 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant