You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I'm curious whether it's feasible to get a more detailed thread state. Specifically, I'd like to be able to determine thread states like:
New/Created: A thread is created but not started yet. This is when the thread object is initialized, but start() has not been called.
Runnable: Once start() is called, the thread is ready to run but might be waiting for CPU scheduling.
Running: The thread is actively running.
Waiting/Blocked: The thread is waiting for a lock, I/O, or another resource. This can happen explicitly (e.g., waiting on a Condition or Event) or implicitly (e.g., during I/O operations).
Terminated/Stopped: After the thread's run() method completes, it moves to the stopped state.
I see that the existing dump output contains:
"active": true,
"owns_gil": false,
Is it feasible to reliably determine these thread states using py-spy's existing infrastructure?
The text was updated successfully, but these errors were encountered:
Hi! I'm curious whether it's feasible to get a more detailed thread state. Specifically, I'd like to be able to determine thread states like:
I see that the existing dump output contains:
Is it feasible to reliably determine these thread states using py-spy's existing infrastructure?
The text was updated successfully, but these errors were encountered: