[Bug 296145] New: Random, nonreproducible crashes in kmail

abrahams at acm.org abrahams at acm.org
Fri Mar 16 12:54:33 GMT 2012


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

            Bug ID: 296145
          Severity: crash
           Version: unspecified
          Priority: NOR
          Assignee: kdepim-bugs at kde.org
           Summary: Random, nonreproducible crashes in kmail
    Classification: Unclassified
                OS: Linux
          Reporter: abrahams at acm.org
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: general
           Product: kmail2

Application: kmail (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.0.0-17-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed: Advancing through list of
emails

Notes:

1. I've had a lot of crashes in kmail recently.  Today I had two within five
minutes.

2. Since there's no clear action that triggers this bug, there's no way to know
if it's a true duplicate of any other kmail bug.  As far as I know I was not
doing anything that I haven't already done successfully many times.

The crash can be reproduced some of the time.

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

Thread 4 (Thread 0x7f2734cab700 (LWP 23657)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f27481b1c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f27481b1d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f2750c9fefc in start_thread (arg=0x7f2734cab700) at
pthread_create.c:304
#4  0x00007f275310a59d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f273439a700 (LWP 23658)):
#0  0x00007f27530fe473 in __GI___poll (fds=<optimized out>, nfds=<optimized
out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f274ba99f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f274ba9a429 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2753a8ec06 in QEventDispatcherGlib::processEvents (this=0x309aff0,
flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f2753a5e3e2 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f2753a5e637 in QEventLoop::exec (this=0x7f2734399dc0, flags=...) at
kernel/qeventloop.cpp:204
#6  0x00007f275395e067 in QThread::exec (this=<optimized out>) at
thread/qthread.cpp:501
#7  0x00007f275396108b in QThreadPrivate::start (arg=0x309a5f0) at
thread/qthread_unix.cpp:298
#8  0x00007f2750c9fefc in start_thread (arg=0x7f273439a700) at
pthread_create.c:304
#9  0x00007f275310a59d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f2731f64700 (LWP 23659)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f2731f63ab0 in ?? ()
#2  0x00007fff205bb7e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f2755d947c0 (LWP 23645)):
[KCrash Handler]
#6  QNetworkAccessHttpBackend::replyDownloadMetaData (this=0x44e7a70,
hm=<optimized out>, sc=<optimized out>, rp=<optimized out>, pu=<optimized out>,
db=<optimized out>, contentLength=-1) at
access/qnetworkaccesshttpbackend.cpp:827
#7  0x00007f2752191299 in QNetworkAccessHttpBackend::qt_static_metacall
(_o=0x44e7a70, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at
.moc/release-shared/moc_qnetworkaccesshttpbackend_p.cpp:91
#8  0x00007f2753a78ba6 in QObject::event (this=0x44e7a70, e=<optimized out>) at
kernel/qobject.cpp:1195
#9  0x00007f2753f82104 in notify_helper (e=0x7f272c0d2d50, receiver=0x44e7a70,
this=0x21bf880) at kernel/qapplication.cpp:4555
#10 QApplicationPrivate::notify_helper (this=0x21bf880, receiver=0x44e7a70,
e=0x7f272c0d2d50) at kernel/qapplication.cpp:4527
#11 0x00007f2753f86f83 in QApplication::notify (this=0x7fff205407d0,
receiver=0x44e7a70, e=0x7f272c0d2d50) at kernel/qapplication.cpp:4416
#12 0x00007f27557b09a6 in KApplication::notify (this=0x7fff205407d0,
receiver=0x44e7a70, event=0x7f272c0d2d50) at
../../kdeui/kernel/kapplication.cpp:311
#13 0x00007f2753a5f5fc in QCoreApplication::notifyInternal
(this=0x7fff205407d0, receiver=0x44e7a70, event=0x7f272c0d2d50) at
kernel/qcoreapplication.cpp:876
#14 0x00007f2753a633ca in sendEvent (event=0x7f272c0d2d50, receiver=0x44e7a70)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
data=0x216a220) at kernel/qcoreapplication.cpp:1500
#16 0x00007f2753a8e773 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#17 postEventSourceDispatch (s=<optimized out>) at
kernel/qeventdispatcher_glib.cpp:279
#18 0x00007f274ba99a5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f274ba9a258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f274ba9a429 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f2753a8eb9f in QEventDispatcherGlib::processEvents (this=0x216bb00,
flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#22 0x00007f275402721e in QGuiEventDispatcherGlib::processEvents
(this=<optimized out>, flags=<optimized out>) at
kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f2753a5e3e2 in QEventLoop::processEvents (this=<optimized out>,
flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f2753a5e637 in QEventLoop::exec (this=0x7fff205406b0, flags=...) at
kernel/qeventloop.cpp:204
#25 0x00007f2753a636c7 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1148
#26 0x0000000000402bd3 in main (argc=<optimized out>, argv=<optimized out>) at
../../kmail/main.cpp:145

Possible duplicates by query: bug 295746, bug 295225, bug 294828, bug 293172,
bug 292991.

Reported using DrKonqi

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



More information about the Kdepim-bugs mailing list