https://bugs.kde.org/show_bug.cgi?id=360137
Bernd Steinhauser changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #28 from Bernd Steinhauser ---
Just to give you some numbers, I let this system run for approximately one day.
During this time, plasmashell (in two threads) on average consumed 20% of one
CPU.
It was then on rank 1, right before Xorg with a
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #27 from Bernd Steinhauser ---
Just wanted to note that I still see this with 5.6.95 and it feels like it
actually got worse.
A lot of stuttering due to plasmashell's high CPU load.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #26 from Bernd Steinhauser ---
Should note: I don't have any rotated screens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #25 from Bernd Steinhauser ---
Hm, bug 362247 gave me an idea.
Normally, I'm using the following driver options for either amdgpu or radeon.
The driver that is used does not matter the behavior is the same:
Option "TearFree" "On"
https://bugs.kde.org/show_bug.cgi?id=360137
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #24 from Bernd Steinhauser ---
For testing purposes, I downgraded Plasma to 5.5.5. I do still see the same
behavior.
I'm pretty sure that I didn't see it previously when I ran 5.5.x, because a
laggy behavior like this I would've noticed.
As
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #23 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #22)
> Smells related to the new feature to show progress in taskitems?
Is there a way to test that? Can I build plasma without it?
Would a bisect help?
--
You are r
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #22 from Thomas Lübking ---
> If I copy a file using dolphin, plasmashell becomes unresponsive.
https://bugs.kde.org/show_bug.cgi?id=311799
https://bugs.kde.org/show_bug.cgi?id=347237
Smells related to the new feature to show progress in t
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #21 from Bernd Steinhauser ---
Now on 5.6.0, this does still happen.
One thing I noticed recently: If I copy a file using dolphin, plasmashell
becomes unresponsive. Like I can't use the task manager to switch screens,
can't use the menu, ri
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #20 from Bernd Steinhauser ---
hw accel for firefox does not make a significant difference.
Tab changing in konsole, kate can also be used to trigger the stuttering.
To me it seemed like it might have something to do with window management,
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #19 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #18)
> Doubleclick sounds like related to bug #357450 but should be resolved in
> your KWin?
I've never had this before updating to 5.5.95. But now that you point me to
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #18 from Thomas Lübking ---
Doubleclick sounds like related to bug #357450 but should be resolved in your
KWin?
About the cross process CPU load I could imagine that this is due to a swapping
race in two GL contexts (your FF is gonna use HW
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #17 from Bernd Steinhauser ---
Well, there is definitely something wrong with kwin as well, but I have yet to
find out the details.
For example, sometimes it does not respond to a double-click on the window
decoration, which should lead to a
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #16 from Thomas Lübking ---
QML users in KWin are
- all window decorations except breeze (and likely oxygen, which you've been
using)
- most tabboxes (except for cover- and flipswitch) - this would be the major
candidate?
- the desktop switc
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #15 from Bernd Steinhauser ---
Yes, I'm sure about that. I will see if I can reproduce it somehow.
Is there a way to find out *what* kwin or plasmashell are doing when those
issues occur?
gdb?
--
You are receiving this mail because:
You ar
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #14 from Thomas Lübking ---
Hopefully not - there should be no blocking dbus calls in KWin.
Are you sure the stutter did not exist from the beginning?
(It sounds more like and could be misdetected triple buffering, ie. KWin
believes your gl
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #13 from Bernd Steinhauser ---
I'm not sure, but it could be related:
Yesterday, after letting the system run for 1 day without restarting anything
desktop-related, I observed a stuttering performance when playing a video. For
that, it did n
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #12 from Thomas Lübking ---
Apparently the taskbar is simply a prominent exposer of "something that makes
qtquick slow", ie. afaiu uses "wrong"/bad QML statements. *shrug*
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=360137
Eike Hein changed:
What|Removed |Added
CC||bhus...@gmail.com
Assignee|h...@kde.org
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #10 from Bernd Steinhauser ---
kded crashes and therefore is not running. See bug 360245.
I've had it running a couple of times and then it complained about blocking
dbus calls.
btw, I haven't seen memory consumption of either kwin or plas
https://bugs.kde.org/show_bug.cgi?id=360137
Thomas Lübking changed:
What|Removed |Added
Component|general |Task Manager
CC|
22 matches
Mail list logo
