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 內容生成。