Actions
Bug #12737
openCancel all async operations on session process' socket when closing
Start date:
06/10/2024
Due date:
% Done:
100%
Estimated time:
Description
It is possible that SessionProcess::readHandler()
is called when the socket has been deleted. Likely this occurs when read()
and stop()
are called near simultaneously.
stop()
will have closed the socket and set it to a nullptr
, but read()
had already been scheduled.
At the moment that the socket closes, readHandler()
is called, with a nullptr
object, causing a segfault.
Ensuring that all operations on the socket are cancelled when the socket closes, ought to resolve this issue.
Updated by Bruce Toll 3 months ago
Probably not identical, but possibly related: #9106.
Updated by Matthias Van Ceulebroeck 2 months ago
- Assignee set to Romain Mardulyn
- Target version changed from 4.11.0 to 4.11.1
Updated by Matthias Van Ceulebroeck about 2 months ago
- Status changed from New to InProgress
Updated by Matthias Van Ceulebroeck about 2 months ago
- Status changed from InProgress to Review
- Assignee changed from Romain Mardulyn to Matthias Van Ceulebroeck
Updated by Matthias Van Ceulebroeck about 1 month ago
- Target version changed from 4.11.1 to 4.11.0
Updated by Matthias Van Ceulebroeck 19 days ago
- Status changed from Review to Implemented @Emweb
- Assignee changed from Matthias Van Ceulebroeck to Romain Mardulyn
- % Done changed from 0 to 100
Actions