Bug 497574 - Crash after adding new feeds
Summary: Crash after adding new feeds
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-12-16 20:16 UTC by Alex Dănilă
Modified: 2025-01-13 08:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/10114/events/dffb16f41045432fb75a9e232a71b294/


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Dănilă 2024-12-16 20:16:17 UTC
Application: akregator (5.22.3 (22.12.3))

ApplicationNotResponding [ANR]: false
Qt Version: 6.7.2
Frameworks Version: 6.8.0
Operating System: Linux 6.12.3-amd64 x86_64
Windowing System: Wayland
Distribution: Debian GNU/Linux trixie/sid
DrKonqi: 6.2.4 [KCrashBackend]

-- Information about the crash:
After adding a new feed Akregator may move slowly and even crash. This may be related to the fact that there are many feeds added, as it seemed to crash more often after adding a few more new feeds.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f00fbde06cc in Akregator::Backend::FeedStorage::lastFetch() const () from /lib/x86_64-linux-gnu/libakregatorprivate.so.5
#5  0x00007f00fbdabb2c in Akregator::Feed::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /lib/x86_64-linux-gnu/libakregatorprivate.so.5
#6  0x00007f00fbdbe82b in Akregator::Folder::slotAddToFetchQueue(Akregator::FetchQueue*, bool) () from /lib/x86_64-linux-gnu/libakregatorprivate.so.5
#7  0x00007f00fa5185fe in QtPrivate::QSlotObjectBase::call (this=0x55710cb4ac70, r=0x55710cb1f290, a=0x7ffc0865a120) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#8  doActivate<false> (sender=0x55710c9c8b50, signal_index=3, argv=0x7ffc0865a120) at kernel/qobject.cpp:3925
#9  0x00007f00fa510dc7 in QMetaObject::activate (sender=<optimized out>, m=m@entry=0x7f00fa7852e0 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc0865a120) at kernel/qobject.cpp:3985
#10 0x00007f00fa51c8be in QTimer::timeout (this=<optimized out>, _t1=...) at .moc/moc_qtimer.cpp:205
#11 0x00007f00fa50b77b in QObject::event (this=0x55710c9c8b50, e=0x7ffc0865a260) at kernel/qobject.cpp:1369
#12 0x00007f00fb163052 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55710c9c8b50, e=0x7ffc0865a260) at kernel/qapplication.cpp:3640
#13 0x00007f00fa4ddcd8 in QCoreApplication::notifyInternal2 (receiver=0x55710c9c8b50, event=0x7ffc0865a260) at kernel/qcoreapplication.cpp:1064
#14 0x00007f00fa4ddec2 in QCoreApplication::sendEvent (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462
#15 0x00007f00fa539f41 in QTimerInfoList::activateTimers (this=0x55710c3a0560) at kernel/qtimerinfo_unix.cpp:643
#16 0x00007f00fa53a86c in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:183
#17 0x00007f00eff0b81f in g_main_dispatch (context=context@entry=0x7f00d4000ed0) at ../../../glib/gmain.c:3357
#18 0x00007f00eff0da57 in g_main_context_dispatch_unlocked (context=0x7f00d4000ed0) at ../../../glib/gmain.c:4208
#19 g_main_context_iterate_unlocked (context=context@entry=0x7f00d4000ed0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4273
#20 0x00007f00eff0e1c0 in g_main_context_iteration (context=0x7f00d4000ed0, may_block=1) at ../../../glib/gmain.c:4338
#21 0x00007f00fa53abed in QEventDispatcherGlib::processEvents (this=0x55710c38cc40, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x00007f00fa4dc642 in QEventLoop::exec (this=this@entry=0x7ffc0865a510, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x00007f00fa4e5062 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x000055710888e8fc in ?? ()
#25 0x00007f00f9c33d68 in __libc_start_call_main (main=main@entry=0x55710888e2e0, argc=argc@entry=1, argv=argv@entry=0x7ffc0865a848) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x00007f00f9c33e25 in __libc_start_main_impl (main=0x55710888e2e0, argc=1, argv=0x7ffc0865a848, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc0865a838) at ../csu/libc-start.c:360
#27 0x000055710888ec81 in ?? ()
[Inferior 1 (process 197295) detached]

Reported using DrKonqi
Comment 1 Laurent Montel 2024-12-27 07:39:33 UTC
akregator 5 is obsolete for sure.
22.12.3 is 2 years ago !
Could you test with last version please ?
I can't reproduce this crash
Comment 2 Alex Dănilă 2024-12-28 14:25:54 UTC
I will come back, but it may take some time until the new Akregator versions become cleanly installable in Debian Unstable. I haven't compiled KDE software from source in some 10 years.
Comment 3 Bug Janitor Service 2025-01-12 03:47:46 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Alex Dănilă 2025-01-13 08:50:12 UTC
Does not repro with 6.3.0 from Debian. 

6.3.0 is also faster and more responsive with many feeds. Thank you for these improvements!