Bug 214050 - Akregator hang while navigating posts
Summary: Akregator hang while navigating posts
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-11 00:01 UTC by Fela Maslen
Modified: 2009-11-12 23:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fela Maslen 2009-11-11 00:01:21 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
If I've selected a feed in akregator with a large number of posts, and navigate the posts quickly by holding down an arrow key, the whole application (kontact or akregator) becomes unresponsive and hangs, requiring a force quit (killall does the job). Akregator should wait till it's loaded the first post before continuing to the next, and the next and so on otherwise the system tries to load all the posts at once.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#11 0x00007fafae87f373 in poll () from /lib/libc.so.6
#12 0x00007fafa2823b90 in ?? () from /lib/libdbus-1.so.3
#13 0x00007fafa2821fdd in ?? () from /lib/libdbus-1.so.3
#14 0x00007fafa280e58e in ?? () from /lib/libdbus-1.so.3
#15 0x00007fafa28109c3 in ?? () from /lib/libdbus-1.so.3
#16 0x00007fafa280ff46 in dbus_connection_send_with_reply_and_block () from /lib/libdbus-1.so.3
#17 0x00007fafad0a4611 in ?? () from /usr/lib/libQtDBus.so.4
#18 0x00007fafad08ecd3 in QDBusConnection::call(QDBusMessage const&, QDBus::CallMode, int) const () from /usr/lib/libQtDBus.so.4
#19 0x00007fafad0ab10c in QDBusAbstractInterface::callWithArgumentList(QDBus::CallMode, QString const&, QList<QVariant> const&) () from /usr/lib/libQtDBus.so.4
#20 0x00007fafad4965ca in ?? () from /usr/lib/libkio.so.5
#21 0x00007fafad495164 in KIO::Slave::createSlave(QString const&, KUrl const&, int&, QString&) () from /usr/lib/libkio.so.5
#22 0x00007fafad48eec3 in ?? () from /usr/lib/libkio.so.5
#23 0x00007fafad490132 in ?? () from /usr/lib/libkio.so.5
#24 0x00007fafad49057d in ?? () from /usr/lib/libkio.so.5
#25 0x00007fafad490794 in KIO::Scheduler::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#26 0x00007fafaef84ddc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#27 0x00007fafaef7ed83 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#28 0x00007fafaf88fefc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x00007fafaf8971ce in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#30 0x00007fafb04c6ab6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#31 0x00007fafaef6fc2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#32 0x00007fafaef9a862 in ?? () from /usr/lib/libQtCore.so.4
#33 0x00007fafaef9825d in ?? () from /usr/lib/libQtCore.so.4
#34 0x00007fafa87e9bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#35 0x00007fafa87ed588 in ?? () from /lib/libglib-2.0.so.0
#36 0x00007fafa87ed6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#37 0x00007fafaef981a6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#38 0x00007fafaf9244be in ?? () from /usr/lib/libQtGui.so.4
#39 0x00007fafaef6e532 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#40 0x00007fafaef6e904 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#41 0x00007fafaef70ab9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#42 0x0000000000403f47 in _start ()

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-12 23:39:16 UTC
Can't reproduce with the development version and the backtrace obtained with killall <app> cannot help.

note: a good way to get a backtrace when an application freeze is to attach gdb to the application as explained here: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB