[DEBUG] Investigate leak_check test failures

[aaronj0]

to investigate the sudden leakcheck failures on our CI (which are not reproducible with py3.12)

[aaronj0]

Okay, this behaviour comes from compiler-research/CppInterOp@76d0600 as confirmed by the CI.

Not necessarily a memory leak, delta rss checks have always been unreliable:

      # The use of arena's, free-lists, etc. means that checking rss remains
      # unreliable, unless looking for consistent jumps, so the leak check will
      # be run M times and only considered failed if it "leaks" every time. In
      # actual practice, the number of fails is 0, 1, or M. Note that the total
      # number of gc objects tracked is always required to remain the same.

Debugging further...

On a separate note, I discovered that currently, the leakcheck tests are only run on the cppyy repo. I will open PR's rectifying this situation. I propose using a requirements.txt file and installing psutil everywhere.

Edit: Still unsure why this is not reproduceable

[aaronj0]

Closing as this debug activity is complete