Skip to content
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

[BUG] wrong color when use hardware acceleration is checked 117+ #191

Open
kzqian opened this issue Nov 10, 2023 · 3 comments
Open

[BUG] wrong color when use hardware acceleration is checked 117+ #191

kzqian opened this issue Nov 10, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@kzqian
Copy link

kzqian commented Nov 10, 2023

Describe the bug
The browser couldn't show correct color when the "Use hardware acceleration when available" is checked. This only happens on my MacBook Air 2018 Intel I5 and under Mojave and for version 117 to 119. Everything looks fine under Catalina or v116 or on my other older MacBook Air 2017.

To Reproduce
Steps to reproduce the behavior:

  1. Go to any site, e.g. https://www.fido.ca

Expected behavior
Site should be showing correctly

Screenshots
With the option checked
Screen Shot 2023-11-10 at 1 35 19 PM

With the option unchecked
Screen Shot 2023-11-10 at 1 35 50 PM

Desktop (please complete the following information):

  • OS: macOS Mojave
  • Build 10.14.6
@kzqian kzqian added the bug Something isn't working label Nov 10, 2023
@kzqian
Copy link
Author

kzqian commented Nov 10, 2023

I disabled GPU rasterization under chrome://flags, and the page can be displayed correctly.
chrome://flags/#enable-gpu-rasterization

@Wowfunhappy
Copy link

Turning off GPU rasterization is probably the right solution. You could try to find a specific "Driver Bug Workaround" (see chrome://gpu/), although I'm not actually sure how to apply those individually.

@Jazzzny
Copy link

Jazzzny commented Jan 27, 2024

Could this be related to removed GPU blocklist items?
These commits in particular look suspicious:

e2c2849 These workarounds only applies to macOS on validating command buffer or on macOS versions Chrome no longer supports.
a5d5158 Remove five macOS gpu workarounds.
8de1453 Chrome's minimum required OS versions are now: Mac >= 10.15
48cdc9d Also removed Mac/Linux entries regarding adjust_src_dst_region_for_blitframebuffer pack_parameters_workaround_with_pack_buffer
98daa5f
e373f0e Removal of "glClearColor does not always work on Intel 6xxx Mac drivers" and "Reset TexImage2D base level to 0 on Intel Mac 10.12.4"

blueboxd pushed a commit that referenced this issue May 16, 2024
Roll Chrome Win64 PGO profile from chrome-win64-6367-1711324243-c17c8603366e04e901055a9ceccb7eba30528a72-6ac91b0d81050d473ed5734235b2f11ed934d4a2.profdata to chrome-win64-6367-1711339532-b487a87910b1f5267746247dee4c711a6745cecb-86072a8a4ae2686ab42b026a94b7aeeb8ed1b235.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-win64-chromium-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Cq-Include-Trybots: luci.chrome-m124.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ib671fdb3697fcb8006ce017e080d5ce4f228582c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5391035
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6367@{#191}
Cr-Branched-From: d158c6d-refs/heads/main@{#1274542}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants