Skip to content

opal/datatype: plug a memory leak in opal_datatype_t destructor #6292

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
merged 1 commit into from
Jan 29, 2019

Conversation

ggouaillardet
Copy link
Contributor

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]

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]>
@ggouaillardet
Copy link
Contributor Author

@bosilca can you please review this ?

I quickly checked the code and at first glance, id from opal_datatype_t is not used (e.g. left untouched at 0) if the datatype is not a predefined one.

@jsquyres
Copy link
Member

bot:ompi:retest

1 similar comment
@hppritcha
Copy link
Member

bot:ompi:retest

@bosilca
Copy link
Member

bosilca commented Jan 29, 2019

All OMPI datatypes are supposed to be created with the id set to -1 (as showed here). In any case using the predefined check is a safe alternative.

@bosilca bosilca merged commit 29915fc into open-mpi:master Jan 29, 2019
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.

4 participants