Base class event_handler_manager closes m_epfd unconditionally in the destructor. But in case of local copy, the constructor exits early and leaves m_epfd initialized as 0.
This leads to closing 0 file descriptor during the local copy destruction what causes runtime issues for objects related to the fd 0.
What
Don't close epfd in event_handler_manager_local destructor.
Why ?
Fix closing of a wrong file description what causes runtime issues.
Change type
What kind of change does this PR introduce?
[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Tests
[ ] Other
Check list
[ ] Code follows the style de facto guidelines of this project
[ ] Comments have been inserted in hard to understand places
Description
Base class event_handler_manager closes m_epfd unconditionally in the destructor. But in case of local copy, the constructor exits early and leaves m_epfd initialized as 0.
This leads to closing 0 file descriptor during the local copy destruction what causes runtime issues for objects related to the fd 0.
What
Don't close epfd in event_handler_manager_local destructor.
Why ?
Fix closing of a wrong file description what causes runtime issues.
Change type
What kind of change does this PR introduce?
Check list