This repository was archived by the owner on Feb 25, 2025. It is now read-only.
Revert skiping illegal render in Dart #49473
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.
This PR reverts the following two PRs:
Effectively,
which means that the illegal renders will take effect in release mode, the mode that the benchmarks are performed in.
This is due to a discovery that the revert #49238 did not bring back the performance. We suspect that some other changes after the culprit (#47239) is also responsible for the regression, which narrows down to just one PR, #47323, which also makes sense. By reverting this change, we'll draw a final conclusion whether the regression is caused by illegal renders.
After this revert, the engine is in a temporary state due to the different behaviors between modes.
Pre-launch Checklist
///
).If you need help, consider asking for advice on the #hackers-new channel on Discord.