Summary: | Restarting Akonadi while it fails to deliver content to frontend makes it crash | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Dennis Schridde <heri+kde> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 | Version Fixed In: | 5.4.3 |
Sentry Crash Report: |
Description
Dennis Schridde
2017-02-12 08:40:35 UTC
Git commit 5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 by Daniel Vrátil. Committed on 23/02/2017 at 18:45. Pushed by dvratil into branch 'Applications/16.12'. DataStream: throw exception if device is null During Connection destruction it can happen that the socket is deleted, but the actual handler is still running and tries to write to that socket (in which case it passes a nullptr to DataStream). This is caused by the issue described in #376822. To prevent the crash in this case (until the root cause is fixed) the DataStream throws an exception if its used without a valid device. This will effectively cause execution to leave the Handler and return. FIXED-IN: 5.4.3 M +5 -2 src/private/datastream_p.cpp M +10 -6 src/private/datastream_p_p.h https://commits.kde.org/akonadi/5219f770b998aad16a3d51bbd4f4c7ceb8b143c9 |