Confirmed users
496
edits
Remote Debugging Protocol: Difference between revisions
→Interacting with Thread-Like Actors
m (→Listing Top-Level Browsing Contexts: If it's italicized, it doesn't need to be capitalized, too.) |
|||
| Line 99: | Line 99: | ||
* <b>Paused</b>: the thread has reported a pause to the client and is awaiting further instructions. In this state, a thread can accept requests and send replies. If the client asks the thread to continue or step, it returns to the "running" state. | * <b>Paused</b>: the thread has reported a pause to the client and is awaiting further instructions. In this state, a thread can accept requests and send replies. If the client asks the thread to continue or step, it returns to the "running" state. | ||
* <b>Exited</b>: the thread has ceased execution, and will disappear. The resources of the underlying thread may have been freed; this state really indicates that the actor's name is not yet available for reuse. | * <b>Exited</b>: the thread has ceased execution, and will disappear. The resources of the underlying thread may have been freed; this state really indicates that the actor's name is not yet available for reuse. When the actor receives a "release" packet, the name may be reused. | ||
[[File:thread-states.png]] | [[File:thread-states.png]] | ||