-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NormObjectTable::Remove(NormObject*): Assertion `__null != tree.Find(theObject->GetId().GetValuePtr(), 8*sizeof(UINT16))' failed #81
Comments
When Python recv RX_OBJECT_NEW , the object may not exist in |
Another probem caused by the unprocessed messages in Log:
notifyCount: 87 mean the length of |
So it may be the case I need to have a mutex associated with access to the rx_table so user application code cannot conflict with the protocol engine code? I'm not 100% certain I understand the cause of the issue but probably a concurrency problem of some sort ...I was trying to keep some of the API calls "lightweight" but may have overlooked something here. I need to investigate this further. |
Since the delay and async-behavior of high-level event process code and low-level NORM code.
User may call
NormObjectCancel
while the object already beenNormSenderNode::AbortObject
by NORM protocol likeNormSenderNode::Sync(NormObjectId objectId)
, which caused object is removed twice in NormSenderNode.rx_table.The text was updated successfully, but these errors were encountered: