Clear finished discrete updates during commit phase #18515
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 6f67d0a:
|
Details of bundled changes.Comparing: bce982b...6f67d0a react-dom
react-art
react-test-renderer
react-native-renderer
react-reconciler
Size changes (stable) |
Details of bundled changes.Comparing: bce982b...6f67d0a react-art
react-native-renderer
react-test-renderer
react-dom
react-reconciler
ReactDOM: size: 0.0%, gzip: 0.0% Size changes (experimental) |
|
I'm not super familiar with this code but it seems a bit fragile. Are we treating the symptom or the cause? You said:
Do we understand why? |
|
Thanks for the unit test! The underlying issue is that we're clearing the timeout without making sure the priority level that corresponds to that level is rescheduled. It's usually fine to clear a pending timeout at the beginning of a new render (in react/packages/react-reconciler/src/ReactFiberRoot.js Lines 216 to 226 in 8edcd03 However, There are multiple ways we could fix this. My instinct is to fix it inside We should also commit your changes here, but let's fix the underlying issue first. I'll take a closer look at this. |
Make sure the suspended level is marked as pinged so that we return back to it later, in case the render we're about to start gets aborted. Generally we only reach this path via a ping, but we shouldn't assume that will always be the case.
If a root is finished at a priority lower than that of the latest pending discrete updates on it, these updates must have been finished so we can clear them now. Otherwise, a later call of `flushDiscreteUpdates` would start a new empty render pass which may cause a scheduled timeout to be cancelled.
|
Thanks again for the fix! 🎉 |
acdlite
added a commit
to acdlite/react
that referenced
this pull request
Apr 8, 2020
Adds a regression test for the same underlying bug as facebook#18515 but using pings. Test already passes, but I confirmed it fails if you revert the fix in facebook#18515.
acdlite
added a commit
that referenced
this pull request
Apr 8, 2020
This was referenced Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix #18020
If a root is finished at a priority lower than that of the latest pending discrete updates on it, these updates must have been finished so we can clear them now. Otherwise, a later call of
flushDiscreteUpdateswould start a new empty render pass which may cause a scheduled timeout to be cancelled.