https://bugs.kde.org/show_bug.cgi?id=404052
Martin Steigerwald changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=404052
BingMyBong changed:
What|Removed |Added
CC|bingmyb...@btinternet.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #17 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=404052
Justin Zobel changed:
What|Removed |Added
Status|CONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=404052
Christoph Feck changed:
What|Removed |Added
CC||bingmyb...@btinternet.com
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #14 from Martin Steigerwald ---
Dan, I just like to remind kindly. This regular crash together with a host of
other issues add up and make the KDEPIM experience with KDEPIM/Akonadi 18.08
quite a bit less enjoyable than with previous
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #13 from Martin Steigerwald ---
Thanks, Christian.
Dan, could you have the look at the valgrind traces I produced? The third one
would be the most accurate one, I believe.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=404052
Christian Hilberg changed:
What|Removed |Added
CC||hilb...@unix-ag.org
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #11 from Martin Steigerwald ---
Created attachment 118575
--> https://bugs.kde.org/attachment.cgi?id=118575=edit
third valgrind run, with all dbgsym package and crash
Another valgrind run. Hopefully this one is enough to find the issue.
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #10 from Martin Steigerwald ---
Created attachment 118539
--> https://bugs.kde.org/attachment.cgi?id=118539=edit
second valgrind run, with error-limit=no
Second valgrind run:
valgrind --error-limit=no --track-origins=yes
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #9 from Martin Steigerwald ---
I have KMail running under valgrind now. Did not like to crash so far, tough.
Once it crashes, it is safe to send the valgrind log to the bugtracker
regarding privacy? It currently is 2,1 MiB and it did not
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #8 from Sandro Knauß ---
The backtrace is now showing the correct traceback and we can see at what line
it went off. But this look fine and you have valid looking this=0x564f98590fb0.
It looks like dvratil already said, like we try to
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #7 from Martin Steigerwald ---
Is this backtrace – after installing libkf5akonadicore5abi2-dbgsym and
libkf5coreaddons5-dbgsym – more useful? I may come around to the valgrind
thing, if still required, next week:
Application: KMail
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #6 from Daniel Vrátil ---
Could you try reproducing under valgrind?
valgrind --track-origins=yes --num-callers=50 kmail &> log.txt
It will be ludicrously slow due to webengine, but it's our only hope figuring
out why it crashes.
--
https://bugs.kde.org/show_bug.cgi?id=404052
Sandro Knauß changed:
What|Removed |Added
CC||dvra...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #4 from Martin Steigerwald ---
Okay, on one hand DrKonqi does not thing the backtraces are related, on the
other hand it truncates the backtrace when I tell it to add it to the bug
report. Since I do not know whether DrKonqi got this right,
https://bugs.kde.org/show_bug.cgi?id=404052
--- Comment #3 from Martin Steigerwald ---
Created attachment 117912
--> https://bugs.kde.org/attachment.cgi?id=117912=edit
New crash information added by DrKonqi
kmail (5.9.3) using Qt 5.11.3
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=404052
Martin Steigerwald changed:
What|Removed |Added
Summary|Crash after filtering |Crash during/after
18 matches
Mail list logo
