https://bugs.kde.org/show_bug.cgi?id=358364
--- Comment #1 from Jan Hudec <b...@ucw.cz> --- 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 watching all bug changes.
