| Summary: | Crashes on startup ever since trying to answer email | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Jan Hudec <bulb> |
| Component: | Assignee: | kdepim bugs <kdepim-bugs> | |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | crash | CC: | kdenis |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Valgrind memcheck trace
One more valgrind trace |
||
|
Description
Jan Hudec
2016-01-22 09:53:30 UTC
I am now certain it started after trying to answer email, because when I started it under valgrind it filtered the invalid write and two composers opened. I am attaching the valgrind memcheck output. There are two invalid writes, presumably one in each composer that starts. The backtraces clearly show they are MessageComposer-related. Unfortunately Debian does not seem to have debug information for the /usr/lib/libkmailprivate.so.4.14.10, which appears on the last line of the stack trace. All of the MessageComposer and everything called from it is decoded correctly though. Hope it helps. Kind regards, Jan Created attachment 96785 [details]
Valgrind memcheck trace
I killed kontact after it started (successfully under valgrind). When I then started it, it crashed again, so I am quite sure the log corresponds to the faulty case.
Created attachment 96786 [details]
One more valgrind trace
When I started it next time, one more message editor came up. However the number of invalid writes remained two. I also noticed some invalid reads there.
The standard error also showed these errors:
kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular reference loop detected in the message tree
kontact(9096) MessageList::Core::ModelPrivate::viewItemJobStepInternalForJobPass1Fill: Circular In-Reply-To reference loop detected in the message tree
kontact(9096) MessageList::Core::ModelPrivate::findMessageParent: Circular In-Reply-To reference loop detected in the message tree
Not sure whether they are related; they appeared long after the point where it would have crashed without valgrind.
I closed the message editors when running under valgrind. Since then, kontact starts up correctly again. This workaround isn't for mere mortals, but presumably there might be some way to remove the draft message via akonadi. I don't know how though; I restarted since it started crashing and something remembered there should be message editor open across it. This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input. |