[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2022-12-17 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=391727 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2022-12-02 Thread Bug Janitor Service
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

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2022-11-17 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=391727 Justin Zobel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2018-03-25 Thread Pali Rohár
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=edit Output from massif In attachment is output from massif. I killed trojita when it consumed more then 1GB of

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2018-03-11 Thread Jan Kundrát
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.

[trojita] [Bug 391727] Trojita crashed when idling in INBOX

2018-03-11 Thread Pali Rohár
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