Open jiri-jirus opened 1 month ago
I came here to report the same. Theres a cause, and easy fix. Slic3r sued to default to the 3d editor view. That view does not spike the CPU or GPU. Now it defaults to the layer preview mode, and that mode is what spikes the CPU/GPU/msedgewebview2 threads. Switching back to editor view immediately fixes the problem. Make Slic3r default back to editor view.
I came here to report the same. Theres a cause, and easy fix. Slic3r sued to default to the 3d editor view. That view does not spike the CPU or GPU. Now it defaults to the layer preview mode, and that mode is what spikes the CPU/GPU/msedgewebview2 threads. Switching back to editor view immediately fixes the problem. Make Slic3r default back to editor view.
sorry, but that is not a fix, but a workaround. msedgewebview2 can never produce spikes & excessive cpu usage. if it is doing this stuff, is it a bug!
I'm experiencing the same with PrusaSlicer 2.8.0 in Windows 10.
I found that CPU usage is high when in the Printer Files tab.
If I switch back to the Dashboard tab, the usage goes down again.
According to '@buhman's comment on #13236 it's related to #12968
Description of the bug
version 2.8.0 spans a lot of msedgewebview2 threads this results in unnecessary high cpu usage when idle. I have set up physical printer with Octoprint API key
Project file & How to reproduce
standard Prusa MK3 printer with Octoprint over LAN with API key - physical printer. Task manager show a number os msedgewebview2.exe processes which consume unnecessary high percent of cpu.
Checklist of files included above
Version of PrusaSlicer
2.8.0
Operating system
Windows 10
Printer model
Prusa MK3