Skip to content

Segmentation Fault in MPI_Finalize if memory is not properly deallocated #2525

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

Closed
rkowalewski opened this issue Dec 6, 2016 · 9 comments
Closed
Assignees
Labels
Milestone

Comments

@rkowalewski
Copy link

OpenMPI (v2.0.1) raises a segmentation fault if we allocate memory for one-sided communication by MPI_Alloc_mem but do not free it by MPI_Free_mem.
I have provided a gist where you can test it. The relevant lines are highlighted. When you execute the statement in line 74 everything works fine. To my best knowledge, the MPI Standard does not require to explicitly free the allocated memory.

Below is some information about my build environment:

$ ompi_info
 Open MPI: 2.0.1
 Open MPI repo revision: v2.0.0-257-gee86e07
 Open MPI release date: Sep 02, 2016
 Open RTE: 2.0.1

$ mpicc --version
 gcc (GCC) 5.4.0
 Copyright (C) 2015 Free Software Foundation, Inc.
@jsquyres jsquyres added this to the v2.0.3 milestone Dec 6, 2016
@jsquyres jsquyres added the bug label Dec 6, 2016
@jsquyres
Copy link
Member

jsquyres commented Dec 6, 2016

@hjelmn Can you have a look?

@rkowalewski
Copy link
Author

I have checked this with the current tarball (see below), same compiler as above. The issue still persists.

  Open MPI: 2.0.2a1
  Open MPI repo revision: d0b97d7
  Open MPI release date: Unreleased developer cop

@jsquyres
Copy link
Member

Ok, thanks for checking.

@hjelmn Had a chance to check into this yet, perchance?

@hppritcha hppritcha modified the milestones: v2.0.3, v2.0.4 Jun 1, 2017
@hppritcha
Copy link
Member

@hjelmn any update for this issue? Should it be moved to future milestone?

@hppritcha
Copy link
Member

hppritcha commented Sep 25, 2017

@rkowalewski I'm trying to reproduce this problem, but so far no success using my IB/Intel OPA cluster. Could you post the content of your config.log as well?

@hppritcha
Copy link
Member

I should say I was using the 2.0.3 release. If you have a chance could you see if the problem is gone with 2.0.3? If its still failing, we will need the config.log.

@jsquyres
Copy link
Member

@rkowalewski Unless you can provide further info, we're going to close this issue.

@rkowalewski
Copy link
Author

I will try to reproduce it until the end of this week, I am actually out of office at the moment.

@jsquyres
Copy link
Member

Excellent -- thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants