Bug 266415 - KMail crashed while trying to view a (too) large email message in the sending folder
Summary: KMail crashed while trying to view a (too) large email message in the sending...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.13.5
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-16 02:46 UTC by Mr. Janne Toivola
Modified: 2012-08-19 11:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mr. Janne Toivola 2011-02-16 02:46:36 UTC
Application: kmail (1.13.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-28-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Tried to send a message that was way too big for Gmail. It got stuck in the sending folder: cannot be sent, cannot be opened for editing without crashing KMail.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa678fdd820 (LWP 6186))]

Thread 2 (Thread 0x7fa650c3a700 (LWP 6188)):
#0  0x00007fa675af2f93 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fa66d4944a9 in ?? () from /lib/libglib-2.0.so.0
#2  0x00007fa66d4948fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007fa67645e566 in QEventDispatcherGlib::processEvents (this=0x19b36f0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414
#4  0x00007fa676433992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007fa676433d6c in QEventLoop::exec (this=0x7fa650c39cf0, flags=) at kernel/qeventloop.cpp:201
#6  0x00007fa67633dd59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487
#7  0x00007fa676414178 in QInotifyFileSystemWatcherEngine::run (this=0x25e59d0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fa676340775 in QThreadPrivate::start (arg=0x25e59d0) at thread/qthread_unix.cpp:248
#9  0x00007fa673f499ca in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007fa675aff70d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fa678fdd820 (LWP 6186)):
[KCrash Handler]
#5  0x00007fa677b3265f in KMCommand::slotStart (this=0xe63d900) at ../../kmail/kmcommands.cpp:265
#6  0x00007fa677b2ad36 in KMCommand::qt_metacall (this=0xe63d900, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4ee893a0) at ./kmcommands.moc:92
#7  0x00007fa676447e3f in QMetaObject::activate (sender=0xe6193f0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xe622228) at kernel/qobject.cpp:3293
#8  0x00007fa67644f65f in QSingleShotTimer::timerEvent (this=0xe6193f0) at kernel/qtimer.cpp:308
#9  0x00007fa676444a63 in QObject::event (this=0xe6193f0, e=0x7fff4ee89b00) at kernel/qobject.cpp:1212
#10 0x00007fa67690822c in QApplicationPrivate::notify_helper (this=0x1a60c40, receiver=0xe6193f0, e=0x7fff4ee89b00) at kernel/qapplication.cpp:4300
#11 0x00007fa67690e6fb in QApplication::notify (this=0x7fff4ee89f70, receiver=0xe6193f0, e=0x7fff4ee89b00) at kernel/qapplication.cpp:4183
#12 0x00007fa678a0ba16 in KApplication::notify (this=0x7fff4ee89f70, receiver=0xe6193f0, event=0x7fff4ee89b00) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007fa67643506c in QCoreApplication::notifyInternal (this=0x7fff4ee89f70, receiver=0xe6193f0, event=0x7fff4ee89b00) at kernel/qcoreapplication.cpp:704
#14 0x00007fa676461d42 in QCoreApplication::sendEvent (this=0x1a8a600) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x1a8a600) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007fa67645e824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 0x00007fa66d4908c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007fa66d494748 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007fa66d4948fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007fa67645e513 in QEventDispatcherGlib::processEvents (this=0x1983000, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#21 0x00007fa6769b846e in QGuiEventDispatcherGlib::processEvents (this=0x25da170, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#22 0x00007fa676433992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#23 0x00007fa676433d6c in QEventLoop::exec (this=0x7fff4ee89da0, flags=) at kernel/qeventloop.cpp:201
#24 0x00007fa676437aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#25 0x0000000000403482 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../kmail/main.cpp:156

Possible duplicates by query: bug 265639, bug 265113, bug 264948, bug 264191, bug 263924.

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2012-08-19 11:06:56 UTC
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding