Google Docs' home page doesn't render with Core Profile |
||||||
Issue descriptionVersion: 54.0.2815.0 (Official Build) canary (64-bit) OS: Mac OS X What steps will reproduce the problem? (1) Launch Canary with --enable-unsafe-es3-apis (2) Navigate to https://docs.google.com/ What is the expected output? Expect to see the drive banner, list of documents, etc. What do you see instead? They're initially displayed but then the window is cleared to white. Resizing, scrolling, etc. only display a white window. I don't know how to track down what's going wrong. Erik, Chris, could either one of you help? This blocks turning on of the Core Profile on Mac.
,
Aug 5 2016
It's probably a type of quad whose shader is incompatible with the Core Profile. enne, danakj, jaydasika, do you have any suggestions for how to track this down?
,
Aug 5 2016
+ericrk When I pass the flag --disable-mac-overlays, the content becomes all black, so not an issue with compositing. When I pass the flag --disable-gpu-rasterization, everything seems to work, both with old and new compositing paths. So the problems lies at the intersection of Ganesh and Core Profile.
,
Aug 8 2016
,
Aug 8 2016
The first failure comes from renderufferStorageMultisample(RENDERBUFFER, 8, BGRA8, 64, 1024). I guess the issue is BGRA8?
,
Aug 8 2016
GL_EXT_bgra isn't exposed in core profile, that's why this fails. The best way to move forward would be for Skia to use RGBA8 instead of BGRA8.
,
Aug 8 2016
Bumping to P1. This shouldn't be hard to fix, and blocks a key feature switch that is desired early during this release branch.
,
Aug 8 2016
Taking a look now - note that it appears you need a non-Intel card to see this (MSAA is blacklisted on intel, and I couldn't repro in that casE).
,
Aug 8 2016
,
Aug 9 2016
Not sure why this bug wasn't auto updated when I committed https://codereview.chromium.org/2227603003/ - but either way, that should have fixed this. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kbr@chromium.org
, Aug 5 2016