Support add new -X option to dump heap and current stack automaticlly when MemoryError has been raised

Feature or enhancement

Proposal:

This idea may be similar to #60585

In the production environment, the memory leak is a common issue for all the developers. For now, we may have two kinds of way to debug it.

1. Intrusive way, we need to modify our code, inject some code to monitor the object malloc, and publish/deploy it again. It will use a lot of time in non-python-code process.
2. Process attach way, we may use the tools like py-spy or other ptrace based way to attach to the process, and dump/analyze the all memory. It's useful but will be limited in the container. For most circumstance, we limit the privilege of the container which is means that the ptrace based way will be unuseable because of the security issue.

I think maybe we can introduce a new -x option to dump heap and current stack automaticlly when MemoryError has been raised just like the developer did in JVM

FYI https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/clopts001.html

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Commencez par examiner cette proposition et l’issue associée #60585, puis comparez le comportement demandé avec l’option Java de dépannage liée. Définissez l’interface de ligne de commande, la sémantique des dumps du tas et de la pile, ainsi que le comportement de MemoryError avant l’implémentation ; la tâche sera considérée comme terminée lorsqu’une conception acceptée et des tests pour la nouvelle option seront disponibles.