Bug 194577 - crash when opening a slashdot page (do not know which)
Summary: crash when opening a slashdot page (do not know which)
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-05-29 18:42 UTC by m.wege
Modified: 2018-10-27 04:07 UTC (History)
2 users (show)

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 m.wege 2009-05-29 18:42:33 UTC
Application that crashed: akregator
Version of the application: 1.4.50
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-020630rc6-generic i686
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Akregator (akregator), signal: Aborted
[KCrash Handler]
#6  0xb8004430 in __kernel_vsyscall ()
#7  0xb5c9e6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb5ca0098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb5ce2633 in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0xb5ce4555 in free () from /lib/tls/i686/cmov/libc.so.6
#11 0xb5ec5231 in operator delete () from /usr/lib/libstdc++.so.6
#12 0xb604196d in QList<QPostEvent>::erase (this=0x85de840, afirst={i = 0xbfe6dfc0}, alast={i = 0x116047b0}) at ../../include/QtCore/../../src/corelib/tools/qlist.h:348
#13 0xb603e368 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x85de828) at kernel/qcoreapplication.cpp:1279
#14 0xb603e5fd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#15 0xb606958f in postEventSourceDispatch (s=0x8601ce0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#16 0xb4d73b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb4d770eb in ?? () from /usr/lib/libglib-2.0.so.0
#18 0xb4d77268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0xb60691d8 in QEventDispatcherGlib::processEvents (this=0x85ff368, flags={i = -1075388056}) at kernel/qeventdispatcher_glib.cpp:324
#20 0xb6596765 in QGuiEventDispatcherGlib::processEvents (this=0x85ff368, flags={i = -1075388008}) at kernel/qguieventdispatcher_glib.cpp:202
#21 0xb603bdda in QEventLoop::processEvents (this=0xbfe6e210, flags={i = -1075387944}) at kernel/qeventloop.cpp:149
#22 0xb603c21a in QEventLoop::exec (this=0xbfe6e210, flags={i = -1075387880}) at kernel/qeventloop.cpp:200
#23 0xb603e6c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#24 0xb64f4a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#25 0x0804f0b1 in main (argc=) at /build/buildd/kdepim-4.2.85/akregator/src/main.cpp:115
Comment 1 Dario Andres 2009-05-29 19:21:50 UTC
Weird , the backtrace only contains Qt calls.
Can you reproduce the crash at will ? Thanks
Comment 2 m.wege 2009-05-30 00:26:54 UTC
No I can't. But there was something special. I had openend a lot of pages and then I got a message, that the server had rejecct me. Then I try reloaded all the pages via Right-click->reload->then it scrashed.
Comment 3 Christoph Feck 2013-09-12 21:42:49 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 4 Andrew Crouthamel 2018-09-24 02:20:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:07:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!