Bug 495834 - Akonadi EWS crash
Summary: Akonadi EWS crash
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: EWS Resource (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-11-05 12:33 UTC by avlas
Modified: 2024-11-05 12:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (86.96 KB, text/plain)
2024-11-05 12:33 UTC, avlas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description avlas 2024-11-05 12:33:31 UTC
Application: akonadi_ews_resource (6.2.2 (24.08.2))

ApplicationNotResponding [ANR]: false
Qt Version: 6.8.0
Frameworks Version: 6.7.0
Operating System: Linux 6.8.0-48-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 6.2
DrKonqi: 6.2.2 [CoredumpBackend]

-- Information about the crash:
I configured the office 365 email account from my university using EWS (imap is not working as it needs oauth2 identification).

At first, everything seems to work fine until it tries to synchronize a folder with almost 30k emails in it, which ruins the experience from there on (synchronization stuck)

Not sure this is because an element in particular or because the long list of elements.

In addition to the backtrace I paste below some messages that appear in the terminal for the case they are useful (some of them appear repeatedly):

rg.kde.pim.ews: Streaming request timeout - restarting
org.kde.pim.ews: itemDetailFetchDone:  0
org.kde.pim.ews.client: Failed to read Subject element - invalid content.
org.kde.pim.ews.client: Invalid Item child: 
org.kde.pim.ews.client: Failed to read EWS request - invalid Item element.
ASSERT: "mChangedItems.size() == mRequest->responses().size()" in file ./resources/ews/ewsfetchitemdetailjob.cpp, line 41
KCrash: Application 'akonadi_ews_resource' crashing... crashRecursionCounter = 2
org.kde.pim.akonadiserver: Subscriber "AgentBaseChangeRecorder - 97429147358336" disconnected
org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_ews_resource" stopped unexpectedly ( "Process failed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_ews_resource' crashed! 0 restarts left.
org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7097180a1300) )
org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7097180a1300) identified as "AgentBaseChangeRecorder - 104427916242160"
Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler.
org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_19 (0x572a260e4c60)
org.kde.pim.ews: Streaming request timeout - restarting

The crash can be reproduced every time.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#9  0x00007da82f44526e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#10 0x00007da82f4288ff in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi
Comment 1 avlas 2024-11-05 12:33:32 UTC
Created attachment 175546 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.