--
You received this message because you are subscribed to the Google Groups "Dart VM Observatory Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to observatory-dis...@dartlang.org.
Hi,You may not get the IsolateRunnable event because it could have happened before your client connected. The correct sequence (as taken from another thread):There is a race in the system if your isolate pauses at start before you subscribe the debug stream- you will not receive an event. Starting up, you should *synchronously* (that is wait on each response) do the following:1) getVersion.2) streamListen(Debug)3) streamListen(Isolate)4) getVM()5) getIsolate(id)
On Mon, Oct 19, 2015 at 11:29 AM 'Devon Carew' via Dart VM Observatory Discuss <observato...@dartlang.org> wrote:--If I spawn a dart vm process with the --pause_isolates_on_start=true and --enable-vm-service flags set, then connect to the service protocol port, is there any guarantee that I'll get the IsolateRunnable event? Will the first client always be notified that there's an isolate ready to be run, or could the event be sent before my client has a chance to connect?If there's a race condition, I assume a more reliable mechanism would be to call getVM(), and use the isolates field on the result to iterate over and start the isolates?--Devon CarewSoftware EngineerGoogle, Inc.
You received this message because you are subscribed to the Google Groups "Dart VM Observatory Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to observatory-dis...@dartlang.org.