https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #20 from Quantum Five ---
Created attachment 97153
--> https://bugs.kde.org/attachment.cgi?id=97153&action=edit
here is the list of all libxcb debugging symbols available on my KUbuntu
install
Which one of them do you need ?
--
You are
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #19 from Quantum Five ---
Hi David,
Unfortunately in KUbuntu there are many debug extensions for libxcb and not one
is called just "libxcb-dbg". No meta package either as far as I can tell. I
will provide a screen shot with all available li
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #18 from Giuseppe Margarita ---
Did you find out something in my log?
I had to return to set "running: false" in that file because plasmashell
process uses 6-7% of CPU load that seems excessive to me for one network and
CPU monitor widget, e
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #17 from David Edmundson ---
>Unfortuantely I can't really see what's going on there as we don't have
>symbols for libxcb (not sure if it's you who needs to install them or me)
Ah found out.
Could you install libxcb debug symbols and redo
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #16 from David Edmundson ---
Your log:
53.71% of the time spent handling X events from the DRI driver saying "I've
done something".
We're getting ~1 million of these events.
How long did you have callgrind on for? It seems excessive.
B
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #15 from Quantum Five ---
Created attachment 97122
--> https://bugs.kde.org/attachment.cgi?id=97122&action=edit
plasmashell serious strains on the CPU after 8+ hours of work
It is true that valgrind (and ONLY valgrind) was running on the
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #14 from Quantum Five ---
Created attachment 97121
--> https://bugs.kde.org/attachment.cgi?id=97121&action=edit
here is my callgrind file as requested
Hope this helps.
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #13 from Quantum Five ---
Created attachment 97115
--> https://bugs.kde.org/attachment.cgi?id=97115&action=edit
CPU load goes back to normal after plasmashell restart
Obvious difference ...There's seems to be a slight drop in the memory
c
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #12 from Quantum Five ---
Created attachment 97114
--> https://bugs.kde.org/attachment.cgi?id=97114&action=edit
plasmashell strain on the CPU with no other programs running
The CPU load generated by plasmashell after ~16 hours of running.
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #11 from Quantum Five ---
Thank you for your help David !
I am currently running valgrind and I'll grab the logs in the evening or
tomorrow morning (I might let it run overnight).
Meanwhile, I have attached two screenshots of "before and a
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #10 from Giuseppe Margarita ---
Created attachment 97113
--> https://bugs.kde.org/attachment.cgi?id=97113&action=edit
Valgrind log 2
Did another.
With two network monitor and one CPU monitor, during reproduction of a YouTube
video, plasm
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #9 from Giuseppe Margarita ---
Created attachment 97112
--> https://bugs.kde.org/attachment.cgi?id=97112&action=edit
Valgrind log
Firts time I use valgrind. Don't know If I did the job well.
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #8 from Giuseppe Margarita ---
(In reply to David Edmundson from comment #7)
> without the change.
>
> also it is marked as being a duplicate of another bug which is tracking a
> practically identical discussion.
OK, I'll do the log when I
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #7 from David Edmundson ---
without the change.
also it is marked as being a duplicate of another bug which is tracking a
practically identical discussion.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #6 from Giuseppe Margarita ---
(In reply to David Edmundson from comment #4)
> Some improvement was added in latest frameworks speeding up a certain event
> filter.
>
>
>
> also I need some sort of logs
>
> Please can you run:
> kquitapp
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #4 from David Edmundson ---
Some improvement was added in latest frameworks speeding up a certain event
filter.
also I need some sort of logs
Please can you run:
kquitapp5 plasmashell
valgrind --tool=callgrind --instr-atstart=no plasmash
https://bugs.kde.org/show_bug.cgi?id=357597
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=357597
--- Comment #3 from Giuseppe Margarita ---
(In reply to Quantum Five from comment #2)
> Unfortunately I can confirm that KUbuntu is also affected ...
>
> I am running KUbuntu 15.10 with all available patched applied from
> ppa:kubuntu-ppa/backports. My
https://bugs.kde.org/show_bug.cgi?id=357597
Quantum Five changed:
What|Removed |Added
CC||hatespam00-bug...@yahoo.com
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=357597
giuseppemargar...@gmail.com changed:
What|Removed |Added
CC||giuseppemargar...@gmail.com
--- Co
https://bugs.kde.org/show_bug.cgi?id=357597
Piotr Dobrogost changed:
What|Removed |Added
CC||p...@bugs.kde.dobrogost.net
--
You are recei
21 matches
Mail list logo
