https://bugs.kde.org/show_bug.cgi?id=391727
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=391727
--- Comment #5 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 b
https://bugs.kde.org/show_bug.cgi?id=391727
Justin Zobel changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=391727
--- Comment #3 from Pali Rohár ---
Created attachment 111632
--> https://bugs.kde.org/attachment.cgi?id=111632&action=edit
Output from massif
In attachment is output from massif. I killed trojita when it consumed more
then 1GB of memory. Output on st
https://bugs.kde.org/show_bug.cgi?id=391727
--- Comment #2 from Jan Kundrát ---
Can you please measure this with some heap profiler so that we know where the
leak is?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=391727
--- Comment #1 from Pali Rohár ---
Same situation, memory usage about 2.7 GB and crash again with following, but
different backtrace:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thread 1 "trojita" received
