OOM in Python-based projects do not show enough info

Examples:
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47038
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47485
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47479

I believe there are missing information in OOM traces on oss-fuzz. The testcase shows that there is too much memory occupied and by which allocations, however the stack trace that identifies those allocations are just about the C part (e.g. in cpython or ASAN themselves). Thus it hides some of the useful info necessary to fix the bug, which is in what part of the fuzzed project (a python project) the allocations are.

Start by reviewing the three linked OSS-Fuzz reports and tracing how OOM information is produced for Python-based projects. Done means OOM traces expose the relevant allocations in the fuzzed Python project rather than only C-level frames.

Written by the indexing model from the issue text.