https://bugs.kde.org/show_bug.cgi?id=438647
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=438647
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=438647
Paul Floyd changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=438647
--- Comment #4 from Paul Floyd ---
And could you also post the _full_ log summary. I would expect something like
==2604== HEAP SUMMARY:
==2604== in use at exit: 8,936 bytes in 5 blocks
==2604== total heap usage: 84 allocs, 79 frees, 25,537 bytes
https://bugs.kde.org/show_bug.cgi?id=438647
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #3 from Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=438647
--- Comment #2 from amita dwivedi ---
Thanks. However I am not disabling leak checks but still not getting any memory
leak summary. Wondering what could be the scenarios when memory leak summary is
not generated in logs. I am getting below valgrind
https://bugs.kde.org/show_bug.cgi?id=438647
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #1 from Tom Hughes
https://bugs.kde.org/show_bug.cgi?id=438647
amita dwivedi changed:
What|Removed |Added
Summary|Not getting leak summary|Not getting memory leak
|
