Thanks guys !
i commited r31816 (bfo: allocate the allocator in init rather than open)
and made a CMR
based on mtt results, i will push George's commit tomorrow.
and based on Rolf recommendation, i will do the CMR by the end of the week
if everything
works fine
Gilles
1 alone.
> 2. Fix it in both bfo and ob1. But needs more testing as ob1 is critical.
>
> Rolf
>
>>-Original Message-
>>From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph
>>Castain
>>Sent: Friday, May 16, 2014 8:54 AM
>>To: Open MPI
: [OMPI devel] RFC : what is the best way to fix the memory leak in
>mca/pml/bfo
>
>Memory isn't supposed to allocated in the "open" call, but only after the
>component is selected (and thus in the "init" call").
>
>
>On May 15, 2014, at 10:57 PM, Gill
Memory isn't supposed to allocated in the "open" call, but only after the
component is selected (and thus in the "init" call").
On May 15, 2014, at 10:57 PM, Gilles Gouaillardet
wrote:
> Folks,
>
> there is a small memory leak in ompi/mca/pml/bfo/pml_bfo_component.c
>
> in my environment, t
Folks,
there is a small memory leak in ompi/mca/pml/bfo/pml_bfo_component.c
in my environment, this module is not used.
this means mca_pml_bfo_component_open() and mca_pml_bfo_component_close()
are invoked but
mca_pml_bfo_component_init() and mca_pml_bfo_component_fini() are *not*
invoked.
mca_p
