Bug 442157 - akonadi_imap_resource freezes and crashes after restart
Summary: akonadi_imap_resource freezes and crashes after restart
Status: RESOLVED DUPLICATE of bug 418844
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 5.18.1
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-08 04:38 UTC by Vadim A. Misbakh-Soloviov (mva)
Modified: 2021-09-08 04:48 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 Vadim A. Misbakh-Soloviov (mva) 2021-09-08 04:38:14 UTC
Application: akonadi_imap_resource (5.18.0 (21.08.0))
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.9.12 x86_64
Windowing System: X11
Drkonqi Version: 5.22.4
Distribution: "Gentoo GNU/Linux"

-- Information about the crash:
Sometimes, one of my imap resources "freezes" (shows no status in KMail accounts dialog), and when I pressing "restart" button, it crashes as follows.
Also it sometimes crashes on (manual) akonadiserver restarts.

Deleting the resource and recreation it from scratch helps for some time, but after som period, it gets that behaviour back...


The crash can be reproduced sometimes.

-- Backtrace:
Application: PDD (akonadi_imap_resource), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fa8e3878069 in QSettings::setValue(QString const&, QVariant const&) () at /usr/lib64/libQt5Core.so.5
#5  0x00007fa8e52006fd in Akonadi::AgentBase::setOnline(bool) () at /usr/lib64/libKF5AkonadiAgentBase.so.5
#6  0x000055726ee145cc in ImapResourceBase::onConnectDone(int, QString const&) ()
#7  0x00007fa8e39073a6 in void doActivate<false>(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5
#8  0x000055726edfa126 in SessionPool::connectDone(int, QString const&) ()
#9  0x000055726ee36314 in SessionPool::declareSessionReady(KIMAP::Session*) ()
#10 0x00007fa8e39073a6 in void doActivate<false>(QObject*, int, void**) () at /usr/lib64/libQt5Core.so.5
#11 0x00007fa8e4d145ac in KJob::result(KJob*, KJob::QPrivateSignal) () at /usr/lib64/libKF5CoreAddons.so.5
#12 0x00007fa8e4d15383 in KJob::finishJob(bool) () at /usr/lib64/libKF5CoreAddons.so.5
#13 0x00007fa8e5355a4a in KIMAP::Job::handleErrorReplies(KIMAP::Response const&) () at /usr/lib64/libKF5IMAP.so.5
#14 0x00007fa8e536aa26 in KIMAP::SessionPrivate::responseReceived(KIMAP::Response const&) () at /usr/lib64/libKF5IMAP.so.5
#15 0x00007fa8e38fff4b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#16 0x00007fa8e43a915f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#17 0x00007fa8e38d90c8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fa8e38dbd37 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#19 0x00007fa8e39240a3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5
#20 0x00007fa8e1a6a4b6 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#21 0x00007fa8e1a6a838 in g_main_context_iterate.constprop () at /usr/lib64/libglib-2.0.so.0
#22 0x00007fa8e1a6a8ef in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fa8e3923b6f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#24 0x00007fa8e38d7b8b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#25 0x00007fa8e38df4e0 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#26 0x000055726ede8a93 in int Akonadi::ResourceBase::init<ImapResource>(int, char**) ()
#27 0x00007fa8e32c67ed in __libc_start_main () at /lib64/libc.so.6
#28 0x000055726ede6c5a in _start ()
[Inferior 1 (process 618569) detached]

Отправить на https://bugs.kde.org/
Comment 1 Vadim A. Misbakh-Soloviov (mva) 2021-09-08 04:48:32 UTC

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