True, it may not be SIGSTOPPED, but just blocked on render. I'm basing my guess on a test I ran where I disabled the lifecycle code in USC and it started working again. But maybe that was coincidence. Or maybe that was related to render blocking instead of SIGSTOP.
True, it may not be SIGSTOPPED, but just blocked on render. I'm basing my guess on a test I ran where I disabled the lifecycle code in USC and it started working again. But maybe that was coincidence. Or maybe that was related to render blocking instead of SIGSTOP.
I'm still investigating