fix: renderer hang in cc BeginMainFrame #16946
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 is just git-import-patches && git-export-patches
deepak1556
approved these changes
Feb 14, 2019
|
Release Notes Persisted
|
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.
Description of Change
This backports a change from Chromium that fixes a rare renderer hang in the
BeginMainFramemethod. The bug in Chromium is view-restricted, but enne@ indicated that this is the change that should fix the issue: https://chromium-review.googlesource.com/c/chromium/src/+/1419132It's already present in m72 so 5-0-x should be fine. https://chromium-review.googlesource.com/c/chromium/src/+/1427521
Checklist
npm testpassesRelease Notes
Notes: Fixed a rare renderer hang in cc::ProxyMain::BeginMainFrame.