Report generated using "--leaks" using pymalloc allocator
This report for memory leaks was generated with the pymalloc allocator active, but without tracking enabled for calls to the pymalloc allocator. This will show confusing results because the pymalloc allocator will retain 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. You should rerun your application with the `PYTHONMALLOC=malloc` environment variable set or pass the `--trace-python-allocators` flag when profiling your application. Click here for more information.