On Tue, Jul 15, 2025 at 2:56 PM cca5507 <cca5...@qq.com> wrote: > > Hi, hackers > > I found the $SUBJECT, the main reason is that RegisteredBgWorker::rw_pid has > not been cleaned. > > Attach a patch to fix it. >
Thank You for reporting this. The problem exists and the patch works as expected. In the patch, we are resetting the PID during shared memory initialization. Is there a better place to handle PID reset in the case of a SIGKILL, possibly within a cleanup flow? For example, during a regular shutdown, we reset the launcher (background worker) PID in CleanupBackend(). Or is this the only possibility? thanks Shveta
