-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
about:gpu differences between Brave and Chrome #3105
Labels
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release/blocking
release-notes/include
Milestone
Comments
bbondy
added
the
priority/P2
A bad problem. We might uplift this to the next planned release.
label
Jan 25, 2019
bbondy
changed the title
about:gpu differences between Brave and Chrome on macOS
about:gpu differences between Brave and Chrome
Jan 25, 2019
bbondy
added
priority/P1
A very extremely bad problem. We might push a hotfix for it.
release/blocking
and removed
priority/P2
A bad problem. We might uplift this to the next planned release.
labels
Jan 25, 2019
This was referenced Jan 25, 2019
@bbondy verified the |
nothing else required. Thanks! |
Verified passed with
Verification passed on
Verification passed on
Verification PASSED on
|
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
priority/P1
A very extremely bad problem. We might push a hotfix for it.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Test-Plan-Specified
QA/Yes
release/blocking
release-notes/include
I verified this with C72 for both Chrome and Brave.
Actual: Viz Service Display Compositor: Disabled on Brave vs enabled on chrome.
Expected: They should be the same
Viz Service Display Compositor
Chrome 71: Disabled
Chrome 72: Enabled
Brave 71: Disabled
Brave 72: Disabled
The text was updated successfully, but these errors were encountered: