Bug 223393 - choqok crashes right after startup
Summary: choqok crashes right after startup
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Unmaintained
Component: general (show other bugs)
Version: SVN
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Andreas Hartmetz
URL:
Keywords:
: 223499 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-01-19 10:43 UTC by Dmitry Suzdalev
Modified: 2010-06-12 19:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Suzdalev 2010-01-19 10:43:24 UTC
Application: choqok (0.9.45)
KDE Platform Version: 4.4.59 (KDE 4.4.59 (KDE 4.5 >= 20100107)) (Compiled from sources)
Qt Version: 4.6.0
Operating System: Linux 2.6.32-ARCH i686
Distribution (Platform): Archlinux Packages

-- Information about the crash:
To reproduce:

1. Start choqok
2. Wait for a crash to happen :-)

Info:
Choqok: 1076663
Qt: 4.6.0 from kde-qt/master
KDE: 1076660

 -- Backtrace:
Application: Choqok (choqok), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5418700 (LWP 20565))]

Thread 2 (Thread 0xb11f3b70 (LWP 20611)):
#0  0xb77c1424 in __kernel_vsyscall ()
#1  0xb6dfe182 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb5f5ddaf in QWaitConditionPrivate::wait (this=0x89a9e34, mutex=0x89a9e30, time=30000) at thread/qwaitcondition_unix.cpp:85
#3  QWaitCondition::wait (this=0x89a9e34, mutex=0x89a9e30, time=30000) at thread/qwaitcondition_unix.cpp:159
#4  0xb5f529fb in QThreadPoolThread::run (this=0x872b508) at concurrent/qthreadpool.cpp:140
#5  0xb5f5cefe in QThreadPrivate::start (arg=0x872b508) at thread/qthread_unix.cpp:244
#6  0xb6df98ac in start_thread () from /lib/libpthread.so.0
#7  0xb5d3d01e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5418700 (LWP 20565)):
[KCrash Handler]
#6  0xb5fa3e09 in QString::operator== (this=0x8a0cffc, other=...) at tools/qstring.cpp:2071
#7  0xb71a2849 in qStringComparisonHelper (s1=..., s2=0xb736ad7f "data") at /home/archuser/kdesvn/kde-qt/include/QtCore/../../src/corelib/tools/qstring.h:908
#8  0xb71c75aa in QString::operator== (this=0x8a0cffc, s=0xb736ad7f "data") at /home/archuser/kdesvn/kde-qt/include/QtCore/../../src/corelib/tools/qstring.h:911
#9  0xb729cd38 in KIO::Slave::holdSlave (protocol=..., url=...) at /home/archuser/kdesvn/kdelibs/kio/kio/slave.cpp:481
#10 0xb729227d in KIO::SchedulerPrivate::heldSlaveForJob (this=0x8713310, job=0x879b650) at /home/archuser/kdesvn/kdelibs/kio/kio/scheduler.cpp:1021
#11 0xb72905ff in heldSlaveForJob (job=0x879b650) at /home/archuser/kdesvn/kdelibs/kio/kio/scheduler.cpp:721
#12 0xb728da16 in SlaveKeeper::takeSlaveForJob (this=0x89095f8, job=0x879b650) at /home/archuser/kdesvn/kdelibs/kio/kio/scheduler.cpp:98
#13 0xb72902d7 in ProtoQueue::startAJob (this=0x89095a0) at /home/archuser/kdesvn/kdelibs/kio/kio/scheduler.cpp:601
#14 0xb7293cc8 in ProtoQueue::qt_metacall (this=0x89095a0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfaab10c) at /home/archuser/kdesvn/build/kdelibs/kio/scheduler_p.moc:190
#15 0xb6062e8a in QMetaObject::metacall (object=0x89095a0, cl=142125648, idx=4, argv=0xbfaab10c) at kernel/qmetaobject.cpp:237
#16 0xb607149b in QMetaObject::activate (sender=0x89095d4, m=0xb6172c64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3294
#17 0xb60c30a7 in QTimer::timeout (this=0x89095d4) at .moc/release-shared/moc_qtimer.cpp:134
#18 0xb607979e in QTimer::timerEvent (this=0x89095d4, e=0xbfaab5d0) at kernel/qtimer.cpp:271
#19 0xb606e304 in QObject::event (this=0x89095d4, e=0x6f0079) at kernel/qobject.cpp:1224
#20 0xb638f50c in QApplicationPrivate::notify_helper (this=0x820ba30, receiver=0x89095d4, e=0xbfaab5d0) at kernel/qapplication.cpp:4242
#21 0xb6396157 in QApplication::notify (this=0xbfaab914, receiver=0x89095d4, e=0xbfaab5d0) at kernel/qapplication.cpp:3661
#22 0xb75c8840 in KApplication::notify (this=0xbfaab914, receiver=0x89095d4, event=0xbfaab5d0) at /home/archuser/kdesvn/kdelibs/kdeui/kernel/kapplication.cpp:302
#23 0xb605dc7b in QCoreApplication::notifyInternal (this=0xbfaab914, receiver=0x89095d4, event=0xbfaab5d0) at kernel/qcoreapplication.cpp:704
#24 0xb608ce66 in QCoreApplication::sendEvent (this=0x820ea34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#25 QTimerInfoList::activateTimers (this=0x820ea34) at kernel/qeventdispatcher_unix.cpp:603
#26 0xb6089b57 in timerSourceDispatch (source=0x820ea70) at kernel/qeventdispatcher_glib.cpp:184
#27 idleTimerSourceDispatch (source=0x820ea70) at kernel/qeventdispatcher_glib.cpp:231
#28 0xb5775378 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb5778bf0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#30 0xb5778d23 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb6089815 in QEventDispatcherGlib::processEvents (this=0x81cf440, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#32 0xb644a915 in QGuiEventDispatcherGlib::processEvents (this=0x81cf440, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#33 0xb605c299 in QEventLoop::processEvents (this=0xbfaab894, flags=) at kernel/qeventloop.cpp:149
#34 0xb605c6ea in QEventLoop::exec (this=0xbfaab894, flags=...) at kernel/qeventloop.cpp:201
#35 0xb606087f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#36 0xb638f5a7 in QApplication::exec () at kernel/qapplication.cpp:3570
#37 0x08055443 in main (argc=5, argv=0xbfaaba74) at /home/archuser/kdesvn/extragear/network/choqok/choqok/main.cpp:56

Reported using DrKonqi
Comment 1 Dmitry Suzdalev 2010-01-19 10:44:49 UTC
Looks like this is a kio bug, reassiging.
Comment 2 Andreas Hartmetz 2010-01-23 00:22:58 UTC
Please check if the crash still happens with kdelibs >= r1078816.
Comment 3 Andreas Hartmetz 2010-01-23 06:17:48 UTC
*** Bug 223499 has been marked as a duplicate of this bug. ***
Comment 4 Andreas Hartmetz 2010-01-23 06:20:23 UTC
I could reproduce the bug and fix it - for me at least. Please reopen if the bug can still be reproduced. Thanks.
Comment 5 Beat Wolf 2010-06-12 19:40:32 UTC
*** Bug 241567 has been marked as a duplicate of this bug. ***