-
Notifications
You must be signed in to change notification settings - Fork 916
Fix/nb leaks #8926
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix/nb leaks #8926
Conversation
a4caa6f
to
aa31cf8
Compare
We need to converge on this and once we reached a consensus we need to apply the same logic to basically all the non-blocking Fortran functions. This includes:
|
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.
LGTM, will approve once the other functions are in 👍
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.
A small formatting nitpick, looks good otherwise.
7507a31
to
301c45e
Compare
Looks like Mellanox build failed with two compile errors:
|
301c45e
to
22ea6a9
Compare
I don't have hcoll on mu clusters, but I think I pushed a fix for this compile error. The PR is ready for final review and them merge. @ggouaillardet and @devreal please one last review, maybe we can make it in the pending releases. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
bc791a2
to
301c45e
Compare
If Fortran and C integers have different sizes we allocate the storage for the C objects in the MPI API. For nonblocking functions we need to release these temporary arrays upon completion of the request in order to avoid memory leaks. Signed-off-by: George Bosilca <bosilca@icl.utk.edu>
301c45e
to
8d9b63d
Compare
@ggouaillardet @devreal can you please re-review? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Austen Lauria <awlauria@us.ibm.com> (cherry picked from commit 4a1c29a)
If that's right can you squash and rebase on current main? |
Closing for #10288 It's a squash of the two commits here and a rebase on top of main. |
A possible fix for #8763