-
Notifications
You must be signed in to change notification settings - Fork 294
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
openamp/rpmsg: fix rpmsg_service memory leak when stop remote #525
Conversation
when remote cannot send destroy message, master cannot call ns_unbind_cb that will cause service cannot release release resources Signed-off-by: Tao Yin <[email protected]>
Seems similar to #508, could you have a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to go.
Please could you explain what do you mean by "little interaction" ? |
yes, you're right, sorry for my inaccurate expression. But the main reason for this modification is that master cannt received NS_DESTORY message, when remote is powered down or exits abnormally. at that time, master needs to actively call ns_unbind_cb to release resources |
@arnopo does this change make sense now? |
As we go to integrate the |
could we close this one as we merge #508? |
I close it as no news Please reopen it if needed |
When remote cannot send destroy messages, master cannot call ns_unbind_cb, this will cause the master to be unable to release resources