Bug 335759

Summary:	kmail crashes on startup due to files in autosave/
Product:	[Applications] kmail2	Reporter:	Mike Frysinger <vapier>
Component:	misc	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	codestruct, jjm, montel
Priority:	NOR
Version:	4.13.1
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:	4.13.2
Attachments:	files in autosave/

Description Mike Frysinger 2014-06-03 17:16:34 UTC

when writing an e-mail, kmail crashed.  now when i try to start it, it crashes every time.  i have to delete ~/.kde4/share/apps/kmail2/autosave/ in order to get it to start up.

Reproducible: Always

Steps to Reproduce:
1. download attached archive
2. unpack it into ~/.kde4/share/apps/kmail2/autosave/
3. start kmail



Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  QTimer::start (this=0x7fffffff7fffffff) at kernel/qtimer.cpp:215
#7  0x00007f1bcc3d4fd1 in KMComposeWin::slotCloseAttachMissingFile (this=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/editor/kmcomposewin.cpp:3524
#8  0x00007f1bcc40ebf5 in KMComposeWin::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1_build/kmail/moc_kmcomposewin.cpp:302
#9  0x00007f1bc70ff358 in QMetaObject::activate (sender=0x24301a0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#10 0x00007f1bc70ff358 in QMetaObject::activate (sender=sender@entry=0x2431040, m=m@entry=0x7f1bc2a59020 <MessageComposer::AttachmentControllerBase::staticMetaObject>, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at kernel/qobject.cpp:3547
#11 0x00007f1bc279f7b3 in MessageComposer::AttachmentControllerBase::fileAttached (this=this@entry=0x2431040) at /var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1_build/messagecomposer/moc_attachmentcontrollerbase.cpp:245
#12 0x00007f1bc279f89e in MessageComposer::AttachmentControllerBase::addAttachment (this=0x2431040, part=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/attachment/attachmentcontrollerbase.cpp:813
#13 0x00007f1bc27c0a72 in MessageComposer::ComposerViewBase::addAttachmentPart (this=this@entry=0x2292e50, partToAttach=<optimized out>) at /var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/composer/composerviewbase.cpp:1215
#14 0x00007f1bc27d084b in MessageComposer::ComposerViewBase::setMessage (this=0x2292e50, msg=...) at /var/tmp/portage/kde-base/kdepim-common-libs-4.13.1/work/kdepim-common-libs-4.13.1/messagecomposer/composer/composerviewbase.cpp:176
#15 0x00007f1bcc3e3d18 in KMComposeWin::setMessage (this=0x22769d0, newMsg=..., lastSignState=<optimized out>, lastEncryptState=<optimized out>, mayAutoSign=<optimized out>, allowDecryption=<optimized out>, isModified=false) at /var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/editor/kmcomposewin.cpp:1600
#16 0x00007f1bcc30d1ed in KMKernel::recoverDeadLetters (this=this@entry=0x7fffc95de320) at /var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/kmkernel.cpp:1132
#17 0x0000000000402f78 in main (argc=<optimized out>, argv=<optimized out>) at /var/tmp/portage/kde-base/kmail-4.13.1/work/kmail-4.13.1/kmail/main.cpp:136

Comment 1 Mike Frysinger 2014-06-03 17:17:37 UTC

Created attachment 86996 [details]
files in autosave/

Comment 2 Laurent Montel 2014-06-03 22:13:16 UTC

already fix in 4.13.2

Comment 3 Gregor Mi 2015-02-28 11:25:00 UTC

Hi, the autosave folder problem can also occur with version 4.14.4:

I composed a mail with a 1 GB attachment which made kontact/kmail crash after hitting the send button. Now there is a 1,4 GB file in the /home/gregor/.kde4/share/apps/kmail2/autosave/ folder which causes a crash when attempting to start kontact or kmail.

Renaming the file from {7695bac9-2ccc-49a7-979d-61e4669e152d} to __{7695bac9-2ccc-49a7-979d-61e4669e152d} caused another crash on startup. Removing the file completely fixed the problem.

Should this bug be reopend or another report be created?

Comment 4 Laurent Montel 2015-02-28 12:53:25 UTC

Do you have a backtrace ?

Comment 5 Gregor Mi 2015-02-28 13:37:35 UTC

I got this on the console:

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
*** KMail got signal 6 (Exiting)
unnamed app(19074): Communication problem with  "kmail2" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" "

Comment 6 Gregor Mi 2015-02-28 13:46:54 UTC

When I start kmail from krunner or kicker (instead of the console) the whole desktop becomes unresponsive here and there until the data is processed.

I can reproduce it by simply putting a random 1 GB file into the autosave folder by hand.

Similar scenario: If I put an mp3 file there (5 MB) kmail opens and the message compose window opens which displays garbage in the editor and then kmail freezes with 25% CPU load. The console shows

** (process:19199): CRITICAL **: enchant_dict_check: assertion 'g_utf8_validate(word, len, NULL)' failed
and every 30 seconds another line is added.