-
-
Notifications
You must be signed in to change notification settings - Fork 357
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
Firefox tab becomes unresponsive when mainsail has been open for a while. #48
Comments
same thing with chrome o OS X, after onne night, the tab take 100% cpu and 1.5go RAM |
@Mechotronic which OS? I haven't had any issue with windows10+chrome, but when using my laptop with arch+firefox, mainsail was slow and using a lot of CPU, I haven't taken the time to test more yet. I should try firefox on windows to compare. v0.8.0-702-gb490848b as well Edit: I played a bit more with my laptop running arch, mainsail seems to run fine on it in chromium but I have the problem in firefox. On my windows computer I had not problems with firefox (but the CPU is much more powerful). Those were short tests. |
@Torreip I'm on windows 10. |
@Mechotronic there goes my theorie then :( do you have the problem with chrome or maybe edge? We should probably start collecting logs when that happens. |
I can confirm on my arch laptop as well, Firefox has virtually 100% cpu fan blowing nut bar....chromium sits pretty stable around 24% cpu ( that is until I go to the dashboard with the webcam going, then it shoots to 100%). Perhaps FF even with the webcam not displayed, for example when your on the console tab, is maybe still running the webcam stuff in the background? And chromium only runs it when the camera is actually displayed? |
I must say, I have noticed this also. Both my machines run FF, windows10 and Ubuntu 18.04. |
I think, it is the temp chart. In the next version, it is completely different. I hope it fix the problem. |
…20' Version. The Klippy state is more definied and should work better now. This work is not finished! feature: display print complete with time and filament used + reprint button bugfix: Fix issue #48. Tempchart need to many load bugfix: Fix issue #46. Print time > 1 day (was a moonraker bug) + format time to "1d 1h" and not "25h" bugfix: Fix issue #39. Mainsail title will show filename Signed-off-by: Stefan Dej <meteyou@gmail.com>
pls recheck this issue with the new version (V0.2.0). if it is fixed, pls close this issue. |
I followed update.md and now I get an error at /printer/info
|
I believe moonraker and klipper are fighting now. I will try and hunt it down:
|
@Mechotronic do you add the UDS in your /etc/default/klipper? |
-a /tmp/klippy_uds" was missing. I added it and rebooted but still have the same error. moonraker doesn't show the status page though, and still shows the error. I removed it and pulled master and ran the install script. It's still broken. I need to fix moonraker first. |
When i made my changes in nano they didn't save for some reason. It's up and running now. I will test the new temp graph and get back to you. Thanks! |
Worked perfect. Thanks again @meteyou ! |
I've noticed that the longer the Mainsail tab is open the slower it gets. Eventually the tab can't be closed normally, and killing the individual tab process returns the browser back to normal. I'm not sue if this is on other browsers.
v0.8.0-702-gb490848b
The text was updated successfully, but these errors were encountered: