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.

首先，在 AWS Fargate 上复现使用长期运行的 ProcessPoolExecutor 及其 initializer 的 Flask 和 Gunicorn 设置。调查 worker 进程中的 profiler 生命周期；当能够收集 executor worker 的 profiling 数据且不会触发 duplicate-profiler-start error 时，即视为完成。

由索引模型根据 Issue 内容生成。