Bug 421077

Summary:	Akonadi crashes after almost any boot
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Peter Huyoff <peter.huyoff>
Component:	server	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	mike, sysop
Priority:	NOR	Keywords:	drkonqi
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	New crash information added by DrKonqi New crash information added by DrKonqi

Description Peter Huyoff 2020-05-05 20:12:52 UTC

Application: akonadiserver (5.14.0 (20.04.0))

Qt Version: 5.14.1
Frameworks Version: 5.69.0
Operating System: Linux 5.6.8-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

Since last OpenSuse Tumbleweed-Update Akonadi crashes after almost any boot. A handful restarts of akonadi later KMail runs normal.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  0x00007ff2524c1544 in QSqlResult::~QSqlResult (this=<optimized out>, __in_chrg=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qhash.h:601
#7  0x00007ff24d2344eb in QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=<optimized out>) at qsql_mysql.cpp:457
#8  QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=<optimized out>) at qsql_mysql.cpp:458
#9  0x00007ff2524b1562 in QSqlQueryPrivate::~QSqlQueryPrivate (this=0x7ff204048920, __in_chrg=<optimized out>) at kernel/qsqlquery.cpp:94
#10 0x00007ff2524b1901 in QSqlQuery::~QSqlQuery (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qsqlquery.cpp:248


Possible duplicates by query: bug 376822.

Reported using DrKonqi

Comment 1 Peter Huyoff 2020-05-05 20:12:52 UTC

Created attachment 128184 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

Comment 2 Mike McCarthy 2020-10-31 10:07:29 UTC

Created attachment 132907 [details]
New crash information added by DrKonqi

akonadiserver (5.14.2 (20.04.2)) using Qt 5.12.7

- What I was doing when the application crashed:

Just logged in. Running in Virtualbox on Windows 10 host.

-- Backtrace (Reduced):
#4  _mm_crc32_u64 (__V=<error reading variable: Cannot access memory at address 0xfe69d8714ca8>, __C=<optimized out>) at /usr/lib64/gcc/x86_64-suse-linux/7/include/smmintrin.h:848
#5  crc32<QChar> (ptr=0xfe69d8714ca8, len=<optimized out>, h=<optimized out>) at tools/qhash.cpp:112
#6  0x00007f355bc48914 in hash (seed=<optimized out>, len=<optimized out>, p=<optimized out>) at tools/qhash.cpp:223
#7  qHash (key=..., seed=<optimized out>) at tools/qhash.cpp:239
#8  0x00005650e742f22b in QHash<QString, Akonadi::Server::AbstractItemRetrievalJob*>::findNode (this=this@entry=0x5650e80ae108, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:934

Comment 3 Justin Zobel 2022-10-30 00:40:28 UTC

Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Mike McCarthy 2022-11-07 11:08:47 UTC

I do not see this behavior any more since I upgraded to OpenSUSE Leap 15.4 (latest).

Comment 5 Bug Janitor Service 2022-11-22 05:12:48 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
mark the bug 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 6 Mike McCarthy 2022-11-22 12:24:25 UTC

Changing status to RESOLVED-WORKSFORME as I can no longer reproduce in latest openSuSE (leap 15.4).