Dear all, In my current company we heavily rely on UITests in oder to test end to end our feature. Our setup has An home made interprocess communication protocol to communicate between the test target and the app target to communicate complex information without affecting Production Code (e.g. into an #IF DEBUG we can command the app the reset his state without relaunching the simulator instance) over 600 UITests (between iPhone and iPad) we don't use yet Swift UI in our application, everything is handled via UIKit (and no storyboards) What we observe is that during a Test session the Test target itself keep allocating memory, storing several Malloc blocks that are never deallocated from memory: we are here talking about queries, assertions, xcwaiter results and so on. From an inspection via the memory debugger we cannot pin point anything related to our current setup, the only visible data is that the memory allocation goes up to about over 800Mb and that the simulator becomes slower and slower. Does anyone observed such behaviour so far? I am also looking at some official documentation on the internal of XCTest and how it handles memory allocation, can anyone pinpoint to a possible solution? Thanks a lot for your attention