https://bugs.kde.org/show_bug.cgi?id=385251
Andrew Crouthamel changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=385251
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #14 from Andrew Croutha
https://bugs.kde.org/show_bug.cgi?id=385251
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #12 from David Edmundson ---
Callgrind doesn't show memory leaks, it shows where CPU time is spent.
massif is the useful tool here.
There is a known (now fixed) memory issue wtih Qt, when using the basic render
loop. You can see this if yo
https://bugs.kde.org/show_bug.cgi?id=385251
Alexander Potashev changed:
What|Removed |Added
CC||aspotas...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=385251
Thomas Bettler changed:
What|Removed |Added
CC||thomas.bett...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=385251
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
--
You are receiving thi
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=385251
Christoph Feck changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
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
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 #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 to
4GB!!
--
You
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 the
https://bugs.kde.org/show_bug.cgi?id=385251
--- Comment #5 from David Edmundson ---
I still don't understand. What is it a stacktrace of?
An arbitrary point in time after clicking?
Is the panel still updating when it's using all this memory?
--
You are receiving this mail because:
You are watc
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 #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 severe...
--
Y
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 be
https://bugs.kde.org/show_bug.cgi?id=385251
David Edmundson changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=385251
David Edmundson changed:
What|Removed |Added
Severity|critical|normal
CC|
19 matches
Mail list logo
