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

Terrible performance in some dropdowns #11003

Closed
2 tasks
sneakythr0ws opened this issue Dec 3, 2021 · 18 comments
Closed
2 tasks

Terrible performance in some dropdowns #11003

sneakythr0ws opened this issue Dec 3, 2021 · 18 comments
Labels
Type: Bug The code does not produce the intended behavior.

Comments

@sneakythr0ws
Copy link

sneakythr0ws commented Dec 3, 2021

Application Version

4.12.1 and previous

Platform

Linux(Ubuntu 21.10 and previous)

Printer

Flyingbear ghost 5

Reproduction steps

Open Material or Nozzle Size choice dropdown.

Actual results

Performance in this dropdown is very very bad.

Expected results

Same performance in all part of system.

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

This drop down works fine:
image
but Material and Nozzle Size have very very bad performance. This dropdowns have different color scheme(white.).Sorry for quality. I can't screenshot it and made a photo with smartphone
image

In preferences dialog performance is good.

@sneakythr0ws sneakythr0ws added the Type: Bug The code does not produce the intended behavior. label Dec 3, 2021
@fvrmr
Copy link
Contributor

fvrmr commented Dec 7, 2021

Hi @sneakythr0ws thank you for your report.
Could you share your log file? You can find your log file here: $HOME/.local/share/cura/<Cura version>/cura.log

@fvrmr fvrmr added the Status: Needs Info Needs more information before action can be taken. label Dec 7, 2021
@sneakythr0ws
Copy link
Author

sneakythr0ws commented Dec 7, 2021

Hi @sneakythr0ws thank you for your report. Could you share your log file? You can find your log file here: $HOME/.local/share/cura/<Cura version>/cura.log

Hi! Sure. But I don't any see changes when I use dropdown(I used tail -f)
cura.log

@no-response no-response bot removed the Status: Needs Info Needs more information before action can be taken. label Dec 7, 2021
@fvrmr
Copy link
Contributor

fvrmr commented Dec 7, 2021

Hi @sneakythr0ws I can't see anything happening in that log. Could you do your reproductions steps: open material and or open nozzle size dropdowns. And after you did that close Cura and again share your log file here.

@fvrmr fvrmr added the Status: Needs Info Needs more information before action can be taken. label Dec 7, 2021
@sneakythr0ws
Copy link
Author

Hi @sneakythr0ws I can't see anything happening in that log. Could you do your reproductions steps: open material and or open nozzle size dropdowns. And after you did that close Cura and again share your log file here.

As I said I tried tail -f cura.log and monitored log when I clicked dropdown. Nothing happened in log.
I think it may be hardware acceleration problem. Is it possible to switch to software api?

@no-response no-response bot removed the Status: Needs Info Needs more information before action can be taken. label Dec 7, 2021
@sneakythr0ws
Copy link
Author

@fvrmr do you need any extra info?

@fieldOfView
Copy link
Collaborator

Recently some users have reported sluggish UI performance in Cura that seems to be caused by a 3rd party component that monitors the network for Ultimaker printers. If you don't have any Ultimaker printers, you could try disabling that module.

Go to the "Installed" tab of the Marketplace, and scroll down to "UM3 Network Printing" and uncheck the checkmark in front of it. Restart Cura and check if the terrible performance is still there.

@sneakythr0ws
Copy link
Author

Recently some users have reported sluggish UI performance in Cura that seems to be caused by a 3rd party component that monitors the network for Ultimaker printers. If you don't have any Ultimaker printers, you could try disabling that module.

Go to the "Installed" tab of the Marketplace, and scroll down to "UM3 Network Printing" and uncheck the checkmark in front of it. Restart Cura and check if the terrible performance is still there.

I tried. But unfortunately no effect. Dropdown controls still have bad performance(

I have problem only in two dropdowns. Look at my screenshots. With dropdowns have different color scheme than main controls and panels. May be this dropdowns use another styles, components, libraries ?

@sneakythr0ws
Copy link
Author

This window has terrible performance too. It takes 5 seconds to enter one character
image

@nallath
Copy link
Member

nallath commented Dec 13, 2021

Could you install and use this plugin to generate some profiling information for us: https://marketplace.ultimaker.com/app/cura/plugins/UltimakerPackages/ExtensiveSupportLogging

@fvrmr fvrmr added the Status: Needs Info Needs more information before action can be taken. label Dec 14, 2021
@no-response no-response bot removed the Status: Needs Info Needs more information before action can be taken. label Dec 15, 2021
@nallath
Copy link
Member

nallath commented Dec 15, 2021

Hmm. I don't really see anything that would explain a slowdown. The rendering update itself seems to take only 2ms, so that's well within the range that one would expect

Could you also run the plugin from startup? It might provide a bit more information.

@sneakythr0ws
Copy link
Author

Hmm. I don't really see anything that would explain a slowdown. The rendering update itself seems to take only 2ms, so that's well within the range that one would expect

Could you also run the plugin from startup? It might provide a bit more information.

I made some extra tests. The problem appears only on external display with fractional scaling
image

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Dec 20, 2021

That's a good hint. Unfortunately on my current computer, my work laptop, using fractional scaling at 125% still causes it to go to 200%. Seems to be a bug in Ubuntu (20.04) there for me.

At home I have a more modern version of Ubuntu (21.10) so maybe I could try it again there.

I suspect that Qt 6.2 will fix this issue by removing use of Controls 1, which seems to be the places where this issue occurs.

@sneakythr0ws
Copy link
Author

That's a good hint. Unfortunately on my current computer, my work laptop, using fractional scaling at 125% still causes it to go to 200%. Seems to be a bug in Ubuntu (20.04) there for me.

At home I have a more modern version of Ubuntu (21.10) so maybe I could try it again there.

I suspect that Qt 6.2 will fix this issue by removing use of Controls 1, which seems to be the places where this issue occurs.

FYI 4.13 beta affected too

@Ghostkeeper
Copy link
Collaborator

Indeed at home the 125% fractional scaling works properly. But the performance of Cura feels normal, even in the drop-downs and pop-ups. I'm not able to reproduce this issue yet.

@sneakythr0ws
Copy link
Author

sneakythr0ws commented Dec 22, 2021

Indeed at home the 125% fractional scaling works properly. But the performance of Cura feels normal, even in the drop-downs and pop-ups. I'm not able to reproduce this issue yet.

For me problem appears only on external 4k monitor. On build-in laptop 4k display even with factional scaling it works properly. Other software works fine.

@Ghostkeeper
Copy link
Collaborator

Ghostkeeper commented Dec 27, 2021

Yes, I have a desktop computer so every monitor is an external monitor. I also have a second "monitor", a 4k projector attached to my computer, which doesn't show the problem either when I turn it on and run Cura on the projector.

@GregValiant GregValiant added Status: Needs Info Needs more information before action can be taken. Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes labels Nov 16, 2024
@GregValiant
Copy link
Collaborator

Is this still an issue in current versions of Cura (5.8.0 and up)? Can this be closed?

@sneakythr0ws
Copy link
Author

Is this still an issue in current versions of Cura (5.8.0 and up)? Can this be closed?

Sure. It works fine

@github-actions github-actions bot removed the Status: Needs Info Needs more information before action can be taken. label Nov 16, 2024
@GregValiant GregValiant removed the Status: Stale ⌛ This issue is over a year old. It might be obsolete or just needs a fresh set of eyes label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

6 participants