[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Denis Kurz]

https://bugs.kde.org/show_bug.cgi?id=358364

Denis Kurz  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UNMAINTAINED

--- Comment #6 from Denis Kurz  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Denis Kurz]

https://bugs.kde.org/show_bug.cgi?id=358364

Denis Kurz  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|UNCONFIRMED |NEEDSINFO
 CC||kde...@posteo.de

--- Comment #5 from Denis Kurz  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Jan Hudec via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358364

--- Comment #2 from Jan Hudec  ---
Created attachment 96785
  --> https://bugs.kde.org/attachment.cgi?id=96785=edit
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Jan Hudec via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358364

Jan Hudec  changed:

   What|Removed |Added

  Component|general |mail

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Jan Hudec via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358364

--- Comment #1 from Jan Hudec  ---
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

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Jan Hudec via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358364

--- Comment #3 from Jan Hudec  ---
Created attachment 96786
  --> https://bugs.kde.org/attachment.cgi?id=96786=edit
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[kontact] [Bug 358364] Crashes on startup ever since trying to answer email

[Jan Hudec via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358364

--- Comment #4 from Jan Hudec  ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs