https://bugs.kde.org/show_bug.cgi?id=488060
--- Comment #9 from Vaclav Fiala ---
> A nice rule of thumb (not requiring any specific rules) could probably be
> following the PID tree. Does the parent process (or more generally any
> ancestor) have focus?
Just as I sent the above, I
https://bugs.kde.org/show_bug.cgi?id=488060
--- Comment #8 from Vaclav Fiala ---
> Do note though that some users are already upset with Wayland limitations so
> the default might never change, but part of what makes KDE so great is the
> possibility of customization, so the curre
https://bugs.kde.org/show_bug.cgi?id=488060
--- Comment #6 from Vaclav Fiala ---
And one more note:
I feel like that in an optimal case the user intent (in form of user initiated
action) should be probably at the center of both solutions (window focus
management / clipboard access). A window
https://bugs.kde.org/show_bug.cgi?id=488060
--- Comment #5 from Vaclav Fiala ---
> Ideally one day we are going to get the "promised" Wayland clipboard
> security feature which prevents programs just reading the clipboard whenever
> they feel like, even if that's an o
https://bugs.kde.org/show_bug.cgi?id=488205
Vaclav Fiala changed:
What|Removed |Added
Status|NEEDSINFO |REOPENED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=488205
--- Comment #8 from Vaclav Fiala ---
> When we don't have solid info it's based on matching Exec lines with desktop
> files. That's all cached, so relatively fast, but it's doing something with
> symlink evaluation in th
https://bugs.kde.org/show_bug.cgi?id=488205
--- Comment #7 from Vaclav Fiala ---
> Can you run `time wl-paste` (the total time will include the time blocked on
> kwin doing all this)
# time wl-paste -n -t text
real0m0,047s
user0m0,000s
sys 0m0,006s
--
Y
https://bugs.kde.org/show_bug.cgi?id=488205
--- Comment #6 from Vaclav Fiala ---
(In reply to David Edmundson from comment #3)
> getpid is cached by glibc, a cache on top wouldn't gain anything.
Well it shows up in a large consecutive sequences in my strace => The syscalls
are made
https://bugs.kde.org/show_bug.cgi?id=488205
--- Comment #2 from Vaclav Fiala ---
One more thing:
Noticed there seem to be quite a lot of getpid() calls sprinkeled in as well.
Caching that (storing the result) could also help performance (avoid context
switch).
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=488205
Vaclav Fiala changed:
What|Removed |Added
Summary|kwin_wayland - high CPU |kwin_wayland - high CPU
|load
https://bugs.kde.org/show_bug.cgi?id=488205
Vaclav Fiala changed:
What|Removed |Added
CC||f...@fedy.cz
--- Comment #1 from Vaclav Fiala
https://bugs.kde.org/show_bug.cgi?id=488205
Bug ID: 488205
Summary: kwin_wayland - high CPU load when requesting clipboard
content (using wl-paste) + weird strace (many readlink
calls on
"/home//)"
Classificatio
12 matches
Mail list logo
