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
As for current version, I see that callbacks are removed from JsonRpcPrivate::m_callbacks only when response with the same ID is recieved. This may lead to memory leak, especially when remote party fails to process a request for some reason (network issues/data loss, reboot, logic error, etc...).
The solution can be to implement a timeout mechanism and event reporting (e.g. callback) to free JsonRpcPrivate::m_callbacks and report this case to caller.
The text was updated successfully, but these errors were encountered:
romansavrulin
changed the title
Delete timed-out callbacks for RPC
Delete timed-out RPC callbacks
Jul 29, 2015
As for current version, I see that callbacks are removed from JsonRpcPrivate::m_callbacks only when response with the same ID is recieved. This may lead to memory leak, especially when remote party fails to process a request for some reason (network issues/data loss, reboot, logic error, etc...).
The solution can be to implement a timeout mechanism and event reporting (e.g. callback) to free JsonRpcPrivate::m_callbacks and report this case to caller.
The text was updated successfully, but these errors were encountered: