normal receiver/sender links are good with the mem leak fix.
however, mgmt operations on mgmt link would become unstable and either fail or report seg fault quite frequently (and of course, sometimes succeed) due to the mem leak fix.
My guessing is that any of the target/source/properties (all of them are from an ATTACH performative) are referenced in the mgmt link (in c amqp_management module) somewhere and they need special treatment (ref counted incorrectly).
revert the change introduced by PR: https://github.com/Azure/azure-uamqp-python/pull/215/files excluding body sequence as it is used by the body sequence feature and needs the fix.
here are the reason for the revert:
need more time for investigation.