| Summary: | Color picker applet is using a lot of CPU resources | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Dmitry Rubtsov <duckrinium> |
| Component: | effects-various | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | duckrinium, kde, me, nate, qydwhotmail, xaver.hugl |
| Priority: | NOR | Flags: | qydwhotmail:
NVIDIA+
|
| Version First Reported In: | 5.26.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Dmitry Rubtsov
2022-10-24 11:50:53 UTC
Cannot reproduce; no CPU spike for me when I click on the dropper but don't pick a color yet. A small update, not entire CPU is being used but seems only one or two physical cores is getting 100% usage by process called plasmashell when I use the color picker. Also trying to record with OBS shows me that Nvidia nvenc encoder failed to respond in 5 seconds, timed out. So it seems to be related to display, not particularly CPU. Again, halts my other apps, Discord for example. It could be me using nvidia gpu, but I'm not sure. Is there a way to profile a widget, without compiling and all that? I have amdgpu and also cannot reproduce. Should blame NVIDIA. Can reproduce with NVIDIA, WTF. Apps being unresponsive is kinda expected side effect, because color picker "freezes" the picture via KWin effects, and lets you select a color. But I certainly didn't expect them to become so unresponsive, up to the point that System Monitor -> History page don't get updated which the picture is "frozen". I can hear the fans go brrrr tho Is this still happening for you in Plasma 6? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |