fix some memleak #13306
fix some memleak #13306
Conversation
avx_component module retain twice by avx_component_op_query and ompi_op_base_op_select function; mca_base_var_register will strdup, and not free old string; opal_patcher_base_framework not close; Signed-off-by: wjjahah <[email protected]>
opal_common_ucx open the opal_memory_base_framework but not close; Signed-off-by: wjjahah <[email protected]>
|
Hi @bosilca , this PR is waiting for workflow approval. Could you please approve it when you have a moment? |
|
@bosilca Looks like you queued up the NVIDIA job last night, but it sat in queue for 10+ hours, so I tried to cancel it. But now it seems stuck. Can you check what's happening on the NVIDIA side? |
|
Sorry, not directly related to the topic of this PR: Why are there queues at Nvidia? I'm having the same problem (13261), and I think 13211 is having the same problem. |
|
@xbw22109 Sorry about this. We actually run CI at a variety of different locations -- not just on Github cloud resources (including NVIDIA). That being said, sometimes something goes wrong on these CI resources, and sometimes they need some care and feeding. That happened with NVIDIA's CI resources this past week; they fixed the issue, but we probably missed some of the pending PRs that falsely failed. I've re-queued the jobs on #13261 and #13211. Sorry for the hassle! 😦 FYI: know that you can also re-trigger CI by pushing a new commit to a PR (even if you |
avx_component module retain twice by avx_component_op_query and ompi_op_base_op_select function;
mca_base_var_register will strdup, and not free old string;
opal_patcher_base_framework not close;