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
There is a potential race condition problem in activityStart/activityStop, because the former shows the spinner dialog in the UI thread, while the latter hides the spinner dialog in the JS thread. So it is possible for activityStop to try to hide the spinner dialog, while it hasn't event been shown yet, if activityStop is executed immediately (or shortly) after activityStart.
For instance, using the following code (e.g. in Chrome remote debugging console):
Bug Report
Problem
There is a potential race condition problem in
activityStart
/activityStop
, because the former shows the spinner dialog in the UI thread, while the latter hides the spinner dialog in the JS thread. So it is possible foractivityStop
to try to hide the spinner dialog, while it hasn't event been shown yet, ifactivityStop
is executed immediately (or shortly) afteractivityStart
.For instance, using the following code (e.g. in Chrome remote debugging console):
What is expected to happen?
activityStop
should always discard a spinner dialog initiated byactivityStart
.What does actually happen?
activityStop
has no effect, because the spinner dialog hasn't been created yet byactivityStart
(due to execution in UI thread).Environment, Platform, Device
Android
Version information
Checklist
The text was updated successfully, but these errors were encountered: