Hi Daniel,
i isolated all the requests and made sure only registration was being processed.
turns out that the problem must be elsewhere as the memory is now stable.
however, the first registration uses a suspend/continue and in this case the xavp memory is not released.

kam.log.gz


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.