[kopete-bugs] [Bug 170684] New: kopete crashes when logging into jabber with large number of users
James
admin at oranged.to
Mon Sep 8 15:52:44 CEST 2008
http://bugs.kde.org/show_bug.cgi?id=170684
Summary: kopete crashes when logging into jabber with large
number of users
Product: kopete
Version: 0.60.1
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kopete-bugs at kde.org
ReportedBy: admin at oranged.to
Version: 0.60.1 (using KDE 4.1.1)
Compiler: 4.2.3
OS: Linux
Installed from: Ubuntu Packages
When I login to our corporate jabber server kopete on kde 4.1.1 crashes. This
does not happen with 3.5.10 or 3.5.9.
It only happens when there are most users logged into the server. If there are
only some users (e.g. outside of business hours) it will not crash.
Application: Kopete (kopete), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59bf940 (LWP 8940)]
[New Thread 0xb31c3b90 (LWP 8962)]
[KCrash handler]
#6 0xb64769bc in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7 0xb785665a in KNetwork::Internal::KSocketBuffer::sendTo (this=0x89b6070,
dev=0x8c58610, len=-1)
at
/build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3socketbuffer.cpp:256
#8 0xb7842689 in KNetwork::KBufferedSocket::slotWriteActivity (
this=0x9c31488)
at
/build/buildd/kde4libs-4.1.1+really4.1.1/kdecore/network/k3bufferedsocket.cpp:349
#9 0xb784246b in KNetwork::KBufferedSocket::qt_metacall (this=0x9c31488,
_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfea9d5c)
at
/build/buildd/kde4libs-4.1.1+really4.1.1/obj-i486-linux-gnu/kdecore/k3bufferedsocket.moc:68
#10 0xb75c1f79 in QMetaObject::activate (sender=0x8c92520,
from_signal_index=4, to_signal_index=4, argv=0xbfea9d5c)
at kernel/qobject.cpp:3016
#11 0xb75c2642 in QMetaObject::activate (sender=0x8c92520, m=0xb76a1a90,
local_signal_index=0, argv=0xbfea9d5c) at kernel/qobject.cpp:3086
#12 0xb75ff6b3 in QSocketNotifier::activated (this=0x8c92520, _t1=24)
at .moc/release-shared/moc_qsocketnotifier.cpp:81
#13 0xb75c860f in QSocketNotifier::event (this=0x8c92520, e=0xbfeaa190)
at kernel/qsocketnotifier.cpp:326
#14 0xb6a83f9c in QApplicationPrivate::notify_helper (this=0x80c9030,
receiver=0x8c92520, e=0xbfeaa190) at kernel/qapplication.cpp:3800
#15 0xb6a88bf9 in QApplication::notify (this=0xbfeaa3e8, receiver=0x8c92520,
e=0xbfeaa190) at kernel/qapplication.cpp:3392
#16 0xb7a9e1c3 in KApplication::notify (this=0xbfeaa3e8, receiver=0x8c92520,
event=0xbfeaa190)
at
/build/buildd/kde4libs-4.1.1+really4.1.1/kdeui/kernel/kapplication.cpp:311
#17 0xb75ad0b9 in QCoreApplication::notifyInternal (this=0xbfeaa3e8,
receiver=0x8c92520, event=0xbfeaa190) at kernel/qcoreapplication.cpp:591
#18 0xb75d8883 in socketNotifierSourceDispatch (source=0x80cbbb8)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 0xb5f97dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb5f9b193 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb5f9b74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb75d89f8 in QEventDispatcherGlib::processEvents (this=0x80c90e8,
flags=@0xbfeaa2d8) at kernel/qeventdispatcher_glib.cpp:325
#23 0xb6b17a25 in QGuiEventDispatcherGlib::processEvents (this=0x80c90e8,
flags=@0xbfeaa308) at kernel/qguieventdispatcher_glib.cpp:204
#24 0xb75ac33d in QEventLoop::processEvents (this=0xbfeaa380,
flags=@0xbfeaa344) at kernel/qeventloop.cpp:149
#25 0xb75ac4cd in QEventLoop::exec (this=0xbfeaa380, flags=@0xbfeaa388)
at kernel/qeventloop.cpp:200
#26 0xb75ae74d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#27 0xb6a83897 in QApplication::exec () at kernel/qapplication.cpp:3330
#28 0x08087efb in ?? ()
#29 0xb6419450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#30 0x080644b1 in _start ()
#0 0xb7f59410 in __kernel_vsyscall ()
--
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the kopete-bugs
mailing list