-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Windows 7: julia.exe
using 100% of a core when idle
#329
Comments
On windows? Which browser? |
Were you running VS Code at the same time? |
Windows 7, Firefox 80.0. And yes, VS Code was running at the same time but I tried without it and the result was the same. |
I tried on my other machine which is on Windows 10 and I can't reproduce the issue (Firefox 80.0 and same version of Julia and Pluto) |
Is the UI still responsive while it is at 100%? There are two If you shut down the notebook from the main menu, one of the processes will disappear. By remembering their CPU and RAM usages, you should be able to tell which one shut down. |
It was the notebook process and the UI was still responsive. |
What happens when you Ctrl+C in the terminal? Does it shut down Pluto normally or do you get a stacktrace |
Here is the console output. The first errors appeared after the page has been loaded in Firefox.
|
Could you write the place where you pressed Ctrl+C inside the output? |
julia.exe
using 100% of a core when idlejulia.exe
using 100% of a core when idle
It was before the line |
It seems if I use plotly() instead of the default GR backend for Plots this behavior doesn't appear. |
Can you try Jupyter? |
@Ummon does this only happen in that particular notebook or for all notebooks? |
This is not a problem for Windows 7 in general, and it is impossible for me to debug, so let's close this for now. |
The following notebook output the correct values but after executing the code the associated notebook process
julia.exe
takes 100% of a whole core of my CPU.I'm using the latest version of Julia (1.5) and Pluto (0.11.10)
The text was updated successfully, but these errors were encountered: