Missing data for processes started with ProcessPoolExecutor

We have a Flask application with Gunicorn running on AWS Fargate. Our application has part of the business logic executed in parallel, using ProcessPoolExecutor. The executor, including the worker processes are reused and long running.
We have noticed that we are missing profiling data for the logic executed in worker processes. We have attempted to start new profiler for worker processes using ProcessPoolExecutor initializer, but this attempt has failed with message that we can't start the profiler twice within the same process.

Comece reproduzindo a configuração do Flask e do Gunicorn com um ProcessPoolExecutor de longa duração e seu initializer no AWS Fargate. Investigue o ciclo de vida do profiler nos processos worker; considera-se concluído quando os dados de profiling dos workers do executor são coletados sem disparar o duplicate-profiler-start error.

Escrita pelo modelo de indexação a partir do texto da issue.