[Bug 283196] New: Kontact crash using 4.7.x git head

Scott Kitterman kde at kitterman.com
Sun Oct 2 19:13:02 UTC 2011


           Summary: Kontact crash using 4.7.x git head
           Product: kontact
           Version: 4.7.1
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: kde at kitterman.com

Application: kontact (4.7.1)
KDE Platform Version: 4.7.1 (4.7.1)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic-pae i686
Distribution: Ubuntu oneiric (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

I was away from the computer and found it crashed when I returned.  The system
is set up to check mail automatically, so there would have been some Kontact
related activity.

kdepim is updated to the 4.7 branch snapshot on October 1 ending at 662e936f.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
[Current thread is 1 (Thread 0xb272a730 (LWP 13977))]

Thread 4 (Thread 0xb1613b70 (LWP 13978)):
#0  0xb77aa424 in __kernel_vsyscall ()
#1  0xb3ceea5c in pthread_cond_wait@@GLIBC_2.3.2 () from
#2  0xb614bcfc in pthread_cond_wait () from /lib/i386-linux-gnu/libc.so.6
#3  0xb58f3883 in WTF::TCMalloc_PageHeap::scavengerThread (this=0xb600f340) at
#4  0xb58f399f in WTF::TCMalloc_PageHeap::runScavengerThread
(context=0xb600f340) at wtf/FastMalloc.cpp:1618
#5  0xb3cead31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0xb613e0ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 3 (Thread 0xb0cf2b70 (LWP 13979)):
#0  0xb77aa424 in __kernel_vsyscall ()
#1  0xb614c063 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0xb60e0135 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xad874b70 (LWP 13983)):
#0  0xb77aa424 in __kernel_vsyscall ()
#1  0xb614c063 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2  0xb60e0135 in ?? () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb272a730 (LWP 13977)):
[KCrash Handler]
#7  0xb77aa424 in __kernel_vsyscall ()
#8  0xb6099c8f in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb609d2b5 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb60cfdfc in ?? () from /lib/i386-linux-gnu/libc.so.6
#11 0xb60dabc2 in ?? () from /lib/i386-linux-gnu/libc.so.6
#12 0xb60db862 in ?? () from /lib/i386-linux-gnu/libc.so.6
#13 0xb60dd411 in ?? () from /lib/i386-linux-gnu/libc.so.6
#14 0xb60deab7 in realloc () from /lib/i386-linux-gnu/libc.so.6
#15 0xb6dfee53 in qRealloc (ptr=0x9235748, size=128) at global/qmalloc.cpp:65
#16 0xb6e52836 in QString::realloc (this=0xbfe03f6c, alloc=54) at
#17 0xb6e52ccd in QString::append (this=0xbfe03f6c, str=...) at
#18 0xb44c09c0 in operator+= (s=<optimized out>, this=<optimized out>) at
#19 QDBusConnectionPrivate::handleSignal (this=0x919e760, msg=...) at
#20 0xb44c24b2 in handleMessage (amsg=<optimized out>, this=<optimized out>) at
#21 QDBusConnectionPrivate::handleMessage (this=0x919e760, amsg=...) at
#22 0xb44c646f in qDBusSignalFilter (connection=0x9235860, message=0x0,
data=0x919e760) at qdbusintegrator.cpp:541
#23 0xb3412441 in dbus_connection_dispatch () from
#24 0xb44b907b in q_dbus_connection_dispatch (connection=<optimized out>) at
#25 QDBusConnectionPrivate::doDispatch (this=0x919e760) at
#26 0xb44bd095 in QDBusConnectionPrivate::socketRead (this=0x919e760, fd=9) at
#27 0xb4500e55 in QDBusConnectionPrivate::qt_metacall (this=0x919e760,
_c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbfe04238) at
#28 0xb6f06b7d in metacall (argv=0xbfe04238, idx=8,
cl=QMetaObject::InvokeMetaMethod, object=0x919e760) at
#29 QMetaObject::metacall (object=0x919e760, cl=QMetaObject::InvokeMetaMethod,
idx=8, argv=0xbfe04238) at kernel/qmetaobject.cpp:232
#30 0xb6f15a6a in QMetaObject::activate (sender=0x91e53a0, m=0xb7037598,
local_signal_index=0, argv=0xbfe04238) at kernel/qobject.cpp:3278
#31 0xb6f64655 in QSocketNotifier::activated (this=0x91e53a0, _t1=9) at
#32 0xb6f1cdff in QSocketNotifier::event (this=0x91e53a0, e=0xbfe04574) at
#33 0xb642bd54 in notify_helper (e=0xbfe04574, receiver=0x91e53a0,
this=0x90d0e80) at kernel/qapplication.cpp:4486
#34 QApplicationPrivate::notify_helper (this=0x90d0e80, receiver=0x91e53a0,
e=0xbfe04574) at kernel/qapplication.cpp:4458
#35 0xb6431103 in QApplication::notify (this=0xbfe04574, receiver=0x91e53a0,
e=0xbfe04574) at kernel/qapplication.cpp:3886
#36 0xb74eb791 in KApplication::notify (this=0xbfe04864, receiver=0x91e53a0,
event=0xbfe04574) at ../../kdeui/kernel/kapplication.cpp:311
#37 0xb6f0019e in QCoreApplication::notifyInternal (this=0xbfe04864,
receiver=0x91e53a0, event=0xbfe04574) at kernel/qcoreapplication.cpp:787
#38 0xb6f2e1d8 in sendEvent (event=0xbfe04574, receiver=<optimized out>) at
#39 socketNotifierSourceDispatch (source=0x90d9510) at
#40 0xb3c1425f in g_main_context_dispatch () from
#41 0xb3c14990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#42 0xb3c14c2a in g_main_context_iteration () from
#43 0xb6f2eada in QEventDispatcherGlib::processEvents (this=0x90ae268,
flags=...) at kernel/qeventdispatcher_glib.cpp:422
#44 0xb64e3e3a in QGuiEventDispatcherGlib::processEvents (this=0x90ae268,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#45 0xb6eff1dd in QEventLoop::processEvents (this=0xbfe047c4, flags=...) at
#46 0xb6eff421 in QEventLoop::exec (this=0xbfe047c4, flags=...) at
#47 0xb6f0419d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#48 0xb64298f4 in QApplication::exec () at kernel/qapplication.cpp:3760
#49 0x0804ac91 in main (argc=) at ../../../kontact/src/main.cpp:218

Possible duplicates by query: bug 206486, bug 176529, bug 174669.

Reported using DrKonqi

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Kdepim-bugs mailing list