Skip to content

Fix hot code replacement event order - #648

Open
Harsh (Mr-KnightCLI) wants to merge 1 commit into
microsoft:mainfrom
Mr-KnightCLI:fix/hcr-event-order
Open

Harsh (Mr-KnightCLI) wants to merge 1 commit into
microsoft:mainfrom
Mr-KnightCLI:fix/hcr-event-order

Conversation

@Mr-KnightCLI

Copy link
Copy Markdown

Fixes #559.

During hot code replacement, ProtocolServer can queue the stopped event while a request is being dispatched but send it immediately otherwise. Sending StoppedEvent before ContinuedEvent makes the delivered order depend on timing; in one path, the UI ends in a running state although the thread is suspended.

Send ContinuedEvent first and StoppedEvent last so the final UI state consistently reflects the suspended thread.

Validation: git diff --check passed. Tests were not run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Race condition at the end of hot code replacement causes inconsistent UI state

1 participant