Skip to content

v4.0.x: opal/datatype: plug a memory leak in opal_datatype_t destructor #6336

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

Merged

Conversation

jsquyres
Copy link
Member

correctly free ptypes if the datatype is not pre-defined.

Thanks Axel Huebl for reporting this.

Refs. #6291

Signed-off-by: Gilles Gouaillardet [email protected]
(cherry picked from commit 7c938f0)

@edgargabriel pointed out this master commit to me; I took the liberty of creating a v4.0.x PR for it.

correctly free ptypes if the datatype is not pre-defined.

Thanks Axel Huebl for reporting this.

Refs. open-mpi#6291

Signed-off-by: Gilles Gouaillardet <[email protected]>
(cherry picked from commit 7c938f0)
@ggouaillardet
Copy link
Contributor

#6348 has to be included (once merged into master) into this PR

Reset ptypes when cloning a datatype in order to prevent
a double free() in the opal_datatype_t destructor.

This fixes a bug introduced in open-mpi/ompi@7c938f0

Fixes open-mpi#6346

Signed-off-by: Gilles Gouaillardet <[email protected]>

(cherry picked from commit open-mpi/ompi@b395342)
@hppritcha hppritcha added the NEWS label Feb 1, 2019
@hppritcha hppritcha merged commit 9e306ce into open-mpi:v4.0.x Feb 11, 2019
bosilca pushed a commit to bosilca/ompi that referenced this pull request Sep 13, 2019
…-destructor-leak

v4.0.x: opal/datatype: plug a memory leak in opal_datatype_t destructor
@jsquyres jsquyres deleted the pr/v4.0.x/fix-datatype-destructor-leak branch September 25, 2019 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants