Skip to content
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

Environment destructor causes error in cleanup #314

Open
aaadelmann opened this issue Oct 2, 2024 · 1 comment
Open

Environment destructor causes error in cleanup #314

aaadelmann opened this issue Oct 2, 2024 · 1 comment
Assignees

Comments

@aaadelmann
Copy link
Member

aaadelmann commented Oct 2, 2024

This was found in OPAX on Gwendolen

partial ==== backtrace (tid:2019130) ====

  1. ...
  2. 13 0x000000000022394b mca_pml_ucx_cleanup() ???:0
  3. 14 0x0000000000082a5f ompi_mpi_finalize() ???:0
  4. 15 0x0000000000d0cbcf ippl::mpi::Environment::~Environment() ???:0
  5. 16 0x000000000045033a std::default_deleteippl::mpi::Environment::operator()() ???:0
  6. 17 0x00000000004501f2 std::unique_ptr<ippl::mpi::Environment, std::default_deleteippl::mpi::Environment >::~unique_ptr() ???:0

It looks like mca_pml_ucx_cleanup( is triggering ompi_mpi_finalize() and subsequently in the Environment destructor

bool Environment::finalized() { int flag = 0; MPI_Finalized(&flag); return (flag != 0); }

In case I do not use Environment::finalized() the error goes away!

@matt-frey
Copy link
Member

MPI_Finalized is only checking if the MPI environment got terminated with MPI_Finalize. I do not understand why the call to Environment::finalized in Environment::~Environment() causes the issue.

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

No branches or pull requests

3 participants