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
When calling __UA_Client_MonitoredItems_create, __UA_Client_Service can close the connection (if receiveServiceResponse returns UA_STATUSCODE_GOODNONCRITICALTIMEOUT), which causes the subscription to be deleted that the monitored item was supposed to be added to.
__UA_Client_MonitoredItems_create does not check if this happened, which then causes the monitored item delete callback to be called during cleanup with nonzero subscription id and non-null subscription context, even though the subscription is already gone.
Background Information / Reproduction Steps
I can reproduce this behaviour by stepping through __UA_Client_Service with a debugger which can trigger the noncriticaltimeout case.
Description
When calling __UA_Client_MonitoredItems_create, __UA_Client_Service can close the connection (if receiveServiceResponse returns UA_STATUSCODE_GOODNONCRITICALTIMEOUT), which causes the subscription to be deleted that the monitored item was supposed to be added to.
__UA_Client_MonitoredItems_create does not check if this happened, which then causes the monitored item delete callback to be called during cleanup with nonzero subscription id and non-null subscription context, even though the subscription is already gone.
Background Information / Reproduction Steps
I can reproduce this behaviour by stepping through __UA_Client_Service with a debugger which can trigger the noncriticaltimeout case.
Checklist
UA_LOGLEVEL
set as low as necessary) attachedThe text was updated successfully, but these errors were encountered: