OPAL MCA memory leaks

[jsquyres]

@hjelmn I see 2 odd memory leaks in opal/runtime/opal_mca.c:

• Line 114: ret = mca_base_var_register ("opal", "opal", NULL, "signal", ...);
• Line 179: ret = mca_base_var_register ("opal", "opal", "net", "private_ipv4",

Neither of these strings are freed at the end of time. I'm guessing the MCA var base is not freeing the "opal" group...? (I see that there's also some "ompi"/"mpi" params registered in this file)

Is there a leak in the MCA var base that doesn't clean up non-framework groups?

[hjelmn]

All variables should be cleaned up with mca_base_var_finalize is called. Is that not being called in this case?

[jsquyres]

That function is being called. But the string storage for these 2 MCA vars are still not freed (according to valgrind). Easy to reproduce:

• Build / install master
• Go into $prefix/lib/openmpi
• mkdir save; mv mca*save
• valgrind orte-info

You move all the other components out just to avoid noise from them. Then the only components left will be the small number of statically-linked components.

When you run orte-info through valgrind, you'll see a few blocks still allocated from these 2 MCA vars.

[jsquyres]

@hjelmn Did this get fixed?

[hjelmn]

Thought I fixed that. Will double-check.

[jsquyres]

K. If fixed, please close this issue.

[hppritcha]

@hjelmn could you check that this issue can be closed.