Add flashImmediateRunning flag to setupSetImmediate #4280
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The problem is caused by recursive
callMicrotasks
calls.Recursive calls appear when we have an event that trigger another event that calls
callMicrotasks
synchronously.In result, we call the same microtasks array multiple times.
In some cases we get the wrong order of instructions and we end up with
runRequested
set ontrue
without callbacks in the queue, so we never callqueueMicrotask
again.The idea of fix is to set flag that inform us, that we are inside
callMicrotasks
call, so we don't execute the same callbacks againTest plan
Animated.ScrollView
components. (one trigger another)