Fix memory leak bug

[Binyang2014]

Fix #533

[liangyuRain]

Also, I wonder if the MR registered in IB should also be properly unregistered in RegisteredMemory's destructor?

mscclpp/src/registered_memory.cc

Line 90 in 7263bb7

const IbMr* mr = contextImpl.getIbContext(ibTransport)->registerMr(data, size);

[Binyang2014]

Also, I wonder if the MR registered in IB should also be properly unregistered in RegisteredMemory's destructor?

mscclpp/src/registered_memory.cc

Line 90 in 7263bb7

const IbMr* mr = contextImpl.getIbContext(ibTransport)->registerMr(data, size);

For MR and QP, thinking if we could wrap it into shared_ptr.

[chhwang]

We need a resource lock so that the removal doesn't happen while there exists unflushed triggers on the flight in the proxy. Also, we need a mechanism that prevents proxies on remote ranks from processing requests on this RegisteredMemory.

[Binyang2014]

I think users are responsible for safely releasing the buffer. Before removing it, ensure that no peers or device-side operations are still accessing this memory. Adding spinlock here to prevent race conditions inside the proxy_channel.

[Binyang2014]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[Binyang2014]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).