Fix for potential memory leak in monitor_t::check_event #482
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The objects eventMsg and addrMsg have the type zmq_msg_t.
Since the event handlers might throw, this could have caused a leak of data associated with eventMsg.
For addrMsg, the constructor of std::string could have thrown ( although this is unlikely ).
This PR replaces raw zmq_msg_t objects with zmq::message_t objects in monitor_t::check_event.