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
We've received a few reports of flutter run hanging, where it looks like the underlying cause is that adb has hung and is only fixed by unplugging and re-plugging the phone in via USB.
This shouldn't cause Flutter to hang and is doing so because we're using Process.runSync() instead of Process.run(), thus pausing the entire isolate until the process exits (which it never does).
`adb` can sometimes hang, which will in turn hang the Dart isolate if
we're using `Process.runSync()`. This changes many of the `Device` methods
to return `Future<T>` in order to allow them to use the async process
methods. A future change will add timeouts to the associated calls so
that we can properly alert the user to the hung `adb` process.
This is work towards #7102, #9567
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
We've received a few reports of
flutter run
hanging, where it looks like the underlying cause is thatadb
has hung and is only fixed by unplugging and re-plugging the phone in via USB.This shouldn't cause Flutter to hang and is doing so because we're using
Process.runSync()
instead ofProcess.run()
, thus pausing the entire isolate until the process exits (which it never does).This is one particular manifestation of #7102
The text was updated successfully, but these errors were encountered: