Report generated using --leaks with an arena allocator
This memory leaks report was generated with the {{metadata.python_allocator}}
allocator active, but without tracking enabled for object
deallocations. This will show misleading results because the
allocator retains memory in memory pools even after the objects
that requested that memory are deallocated, and Memray won't be
able to distinguish memory set aside for reuse from leaked memory.
For a more useful memory leaks report, you should pass the
--trace-python-allocators flag when profiling your application.
Click here for more information.