SocketInitiator::getHost call Dictionary.has may have thread problem · Issue #613 · quickfix/quickfix · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Release 1.15.1, there appears to be a potential thread safety issue with the Dictionary::has method. This method utilizes std::map's find function to retrieve session configurations, which is not thread-safe. It is being employed across various thread contexts, including the main application thread, the socketInitiator's start_thread, the HttpServer's start_thread, and the socketAcceptor's startThread. This could lead to a segmentation fault, as illustrated in the following example:
The text was updated successfully, but these errors were encountered:
In Release 1.15.1, there appears to be a potential thread safety issue with the Dictionary::has method. This method utilizes std::map's find function to retrieve session configurations, which is not thread-safe. It is being employed across various thread contexts, including the main application thread, the socketInitiator's start_thread, the HttpServer's start_thread, and the socketAcceptor's startThread. This could lead to a segmentation fault, as illustrated in the following example:

The text was updated successfully, but these errors were encountered: