Skip to content

dwds VM Service API do not wait for isolate initialization after hot restart #1304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
annagrin opened this issue Apr 15, 2021 · 0 comments · Fixed by #1305
Closed

dwds VM Service API do not wait for isolate initialization after hot restart #1304

annagrin opened this issue Apr 15, 2021 · 0 comments · Fixed by #1305
Assignees
@annagrin

Comments

@annagrin
Copy link
Contributor

Dart devtools sometimes gets erroneous isolate information from dwds in the middle of hot restart,
for example, getIsolate does not wait for initializations of the new isolate after restart and returns
an isolate with null ID.

This seems to cause various issues after hot restart, including exceptions in debug console, non-working
layout explorer, and disabled breakpoints in the UI - see example in the issue below:

Related: flutter/flutter#74903
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@annagrin annagrin

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Initialize new isolate after restart annagrin/webdev
1 participant
@annagrin