Hi @Haven,
Thank you for the report, this is indeed an issue with positional tracking gen 2 in version 4.2.2 of the SDK, we have reproduced it and are working on a fix for this.
A temporary solution would be to set the PositionalTrackingParameters.enable_imu_fusion to false, for which the memory build up should not happen.