Bug 294237

Summary: Akgregator crashes while switching feeds
Product: [Applications] akregator Reporter: swburdine
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: adaptee
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description swburdine 2012-02-16 14:03:54 UTC
Application: akregator (4.7.3)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic x86_64
Distribution: Linux Mint 12 Lisa

-- Information about the crash:
- What I was doing when the application crashed: I was switching from one feed to the next when it crashed. It has done this twice with  different feeds.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f9a818c42ca in type (this=0x7f9a65b57800) at ../../kjs/value.h:452
#7  KJS::cloneInternal (exec=0x2de0510, ctx=0x2de04f0, in=0x7f9a65b57800, path=...) at ../../khtml/ecma/kjs_data.cpp:37
#8  0x00007f9a818c4763 in KJS::encapsulateMessageEventData (exec=0x2de0510, ctx=<optimized out>, data=<optimized out>) at ../../khtml/ecma/kjs_data.cpp:117
#9  0x00007f9a818c4955 in KJS::DelayedPostMessage::execute (this=0x6abff70, w=<optimized out>) at ../../khtml/ecma/kjs_data.cpp:169
#10 0x00007f9a81879c8b in KJS::Window::afterScriptExecution (this=0x7f9a647f0000) at ../../khtml/ecma/kjs_window.cpp:1327
#11 0x00007f9a81880d1e in KJS::WindowQObject::timerEvent (this=0x2d45740) at ../../khtml/ecma/kjs_window.cpp:2481
#12 0x00007f9a84c0a789 in QObject::event (this=0x2d45740, e=<optimized out>) at kernel/qobject.cpp:1181
#13 0x00007f9a855f4474 in notify_helper (e=0x7fff4441d5d0, receiver=0x2d45740, this=0x24110a0) at kernel/qapplication.cpp:4486
#14 QApplicationPrivate::notify_helper (this=0x24110a0, receiver=0x2d45740, e=0x7fff4441d5d0) at kernel/qapplication.cpp:4458
#15 0x00007f9a855f92e1 in QApplication::notify (this=0x7fff4441d8b0, receiver=0x2d45740, e=0x7fff4441d5d0) at kernel/qapplication.cpp:4365
#16 0x00007f9a86309466 in KApplication::notify (this=0x7fff4441d8b0, receiver=0x2d45740, event=0x7fff4441d5d0) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x00007f9a84bf3afc in QCoreApplication::notifyInternal (this=0x7fff4441d8b0, receiver=0x2d45740, event=0x7fff4441d5d0) at kernel/qcoreapplication.cpp:787
#18 0x00007f9a84c20d62 in sendEvent (event=0x7fff4441d5d0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x240f420) at kernel/qeventdispatcher_unix.cpp:603
#20 0x00007f9a84c1e538 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#21 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#22 0x00007f9a7f208a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007f9a7f209258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007f9a7f209429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x00007f9a84c1eed6 in QEventDispatcherGlib::processEvents (this=0x23d9170, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#26 0x00007f9a8569c10e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#27 0x00007f9a84bf2cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#28 0x00007f9a84bf2ef7 in QEventLoop::exec (this=0x7fff4441d860, flags=...) at kernel/qeventloop.cpp:201
#29 0x00007f9a84bf7789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#30 0x0000000000407dac in main (argc=<optimized out>, argv=<optimized out>) at ../../../akregator/src/main.cpp:103

This bug may be a duplicate of or related to bug 261403.

Possible duplicates by query: bug 292992, bug 292308, bug 291864, bug 290555, bug 290222.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-02-16 14:57:28 UTC

*** This bug has been marked as a duplicate of bug 261403 ***