https://bugs.kde.org/show_bug.cgi?id=416049
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #11 from Phil KdeBugs ---
what extra information can I provide? It locks up, goes into a memory dive
quite frequently...!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372447
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=372447
--- Comment #7 from Phil KdeBugs ---
Hi,
This might help. My workstation has 256GB of memory, so I had plenty of time to
catch plasmashell in the act of chewing up all the memory it could. When I
first caught it , it has reached 1.5GB!!
This is a
https://bugs.kde.org/show_bug.cgi?id=372447
--- Comment #8 from Phil KdeBugs ---
Created attachment 108109
--> https://bugs.kde.org/attachment.cgi?id=108109&action=edit
valgrind , shows massive memory allocation. Does not run sufficiently to
profiel
Valgrind. Some direction of what
https://bugs.kde.org/show_bug.cgi?id=385251
Bug ID: 385251
Summary: catastrophic memory leak triggered by panel
interaction
Product: plasmashell
Version: master
Platform: Debian stable
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #2 from Phil KdeBugs ---
Hi,
I just installed the dbsyms for the following:
libqt5core5a-dbgsym
libqt5gui-dbgsym
libqt5gui5-dbgsym
Version: 5.7.1+dfsg-3+b1
I will try and grab a better annotated trace.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #3 from Phil KdeBugs ---
I just noticed(!) checking 381000 how old my version seems to be , even though
this is clean install of stretch.
I'm happy to try a more recent version (if this is fixed), though it does seem
quite s
https://bugs.kde.org/show_bug.cgi?id=385469
Bug ID: 385469
Summary: plasma discover crashes on start
Product: Discover
Version: 5.8.5
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
https://bugs.kde.org/show_bug.cgi?id=385251
Phil KdeBugs changed:
What|Removed |Added
Attachment #108113|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #6 from Phil KdeBugs ---
Hi,
OK I recompiled valgrind to make the RLIMIT 256MB (vs 8MB default) to raise the
limit before we get brk errors.
I turned on the instrumentation after the start up sequence. I then took dumps
before and after
https://bugs.kde.org/show_bug.cgi?id=352742
Phil KdeBugs changed:
What|Removed |Added
CC||phil3em...@earthlink.net
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #7 from Phil KdeBugs ---
Created attachment 108235
--> https://bugs.kde.org/attachment.cgi?id=108235&action=edit
a collection of callgrind reports
Collection of callgrind before and after memory leak runaway, all the way
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #8 from Phil KdeBugs ---
if you want a tar.gz of of text files I can send, but not sure how to upload so
I put them in a pdf.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #9 from Phil KdeBugs ---
to be clear - the panel completely locks up. Fortunately , alt-tab can expose a
terminal to run the commands. I assumed that was obvious due to the excessive
(4GB!) memory use.
Callgrind slows the execution such, I
15 matches
Mail list logo
