Description

A memleak was found in cpython 3.11.0 that looks to potentially be reasonably serious.
Upstream issue is python/cpython#99205
This uses the merged upstream patch python/cpython#99301 until we bump to a newer release (3.11.1+)

Motivation and context

Stable Android/apple

How has this been tested?

Upstream cpython

What is the effect on users?

Potentially more stable memory usage

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

Checklist:

• My code follows the Code Guidelines of this project
• My change requires a change to the documentation, either Doxygen or wiki
• I have updated the documentation accordingly
• I have read the Contributing document
• I have added tests to cover my change
• All new and existing tests passed