[kmail2] [Bug 322189] New: Crash when change of folder interrupted email rendering

[Mário Rodrigues]

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

            Bug ID: 322189
           Summary: Crash when change of folder interrupted email
                    rendering
    Classification: Unclassified
           Product: kmail2
           Version: unspecified
          Platform: Debian stable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: commands and actions
          Assignee: kdepim-bugs at kde.org
          Reporter: mjfr at ua.pt

Application: kmail (1.13.7)
KDE Platform Version: 4.8.4 (4.8.4)
Qt Version: 4.8.2
Operating System: Linux 3.2.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 7.1 (wheezy)

-- Information about the crash:
- What I was doing when the application crashed:
  while retrieving an email I changed the folder I wanted to view

- Custom settings of the application:
  IMAP connection to an exchange server

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x00007fde50ad7f26 in KMAcctImap::ignoreJobsForFolder (this=0x1a07cd0,
folder=0x166a2e0) at ./kmacctimap.moc:116
#7  0x00007fde50c0ffdb in stop (this=0x154c430) at
../../kmail/kmfoldersearch.cpp:235
#8  KMSearch::stop (this=0x154c430) at ../../kmail/kmfoldersearch.cpp:217
#9  0x00007fde50c10697 in KMFolderSearch::executeSearch (this=0x186eb00) at
../../kmail/kmfoldersearch.cpp:432
#10 0x00007fde4f89554f in QMetaObject::activate (sender=0x18779d0, m=<optimized
out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#11 0x00007fde4f89485c in QObject::event (this=0x18779d0, e=<optimized out>) at
kernel/qobject.cpp:1157
#12 0x00007fde4fdb470c in QApplicationPrivate::notify_helper
(this=this at entry=0x1290100, receiver=receiver at entry=0x18779d0,
e=e at entry=0x7fff3f4d4130) at kernel/qapplication.cpp:4556
#13 0x00007fde4fdb8b8a in QApplication::notify (this=0x7fff3f4d4700,
receiver=0x18779d0, e=0x7fff3f4d4130) at kernel/qapplication.cpp:4417
#14 0x00007fde51a14886 in KApplication::notify (this=0x7fff3f4d4700,
receiver=0x18779d0, event=0x7fff3f4d4130) at
../../kdeui/kernel/kapplication.cpp:311
#15 0x00007fde4f87fb5e in QCoreApplication::notifyInternal
(this=0x7fff3f4d4700, receiver=0x18779d0, event=0x7fff3f4d4130) at
kernel/qcoreapplication.cpp:915
#16 0x00007fde4f8b0a52 in sendEvent (event=0x7fff3f4d4130, receiver=<optimized
out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#17 QTimerInfoList::activateTimers (this=0x128e7b0) at
kernel/qeventdispatcher_unix.cpp:611
#18 0x00007fde4f8adc04 in timerSourceDispatch (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:186
#19 timerSourceDispatch (source=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:180
#20 0x00007fde46c40355 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fde46c40688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fde46c40744 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fde4f8ae276 in QEventDispatcherGlib::processEvents (this=0x1207b00,
flags=...) at kernel/qeventdispatcher_glib.cpp:424
#24 0x00007fde4fe5583e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007fde4f87e8af in QEventLoop::processEvents
(this=this at entry=0x7fff3f4d43a0, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007fde4f87eb38 in QEventLoop::exec (this=0x7fff3f4d43a0, flags=...) at
kernel/qeventloop.cpp:204
#27 0x00007fde4f883cf8 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1187
#28 0x0000000000402fe6 in main (argc=<optimized out>, argv=<optimized out>) at
../../kmail/main.cpp:158

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