[Akonadi] [Bug 376385] Restarting Akonadi while it fails to deliver content to frontend makes it crash

[Daniel Vrátil]

https://bugs.kde.org/show_bug.cgi?id=376385

Daniel Vrátil <dvratil at kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://commits.kde.org/ako
                   |                            |nadi/5219f770b998aad16a3d51
                   |                            |bbd4f4c7ceb8b143c9
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED
   Version Fixed In|                            |5.4.3

--- Comment #1 from Daniel Vrátil <dvratil at kde.org> ---
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

-- 
You are receiving this mail because:
You are the assignee for the bug.