New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 632427 link

Starred by 2 users
Status: Duplicate
Merged: issue 633659
Owner:
ericrk@chromium.org
Closed: Aug 2016
Cc:
█ tkonch...@chromium.org
ccameron@chromium.org
erikc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Page does not display with embedded SVG when GPU rasterization is enabled

Reported by brian.ch...@gmail.com, Jul 28 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2809.0 Safari/537.36

Example URL:
http://output.jsbin.com/geboba

Steps to reproduce the problem:
1. Embed an SVG in DOM (directly, not using img
2. Add additional DOM content

What is the expected behavior?
The SVG and the DOM content around it should display correctly.

What went wrong?
The SVG and most of the rest of the page are blank. Some trivial SVGs do work fine, but I've tried a few more complex ones, such as the example linked above, and those don't work.

Works fine in Firefox, Safari and Chrome 52. Does not work in Canary 54.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes Chrome 52

Does this work in other browsers? Yes 

Chrome version: 54.0.2809.0  Channel: n/a
OS Version: OS X 10.11.6
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by tkonch...@chromium.org, Jul 29 2016

Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Tested the same on mac 10.11.5 chrome version 54.0.2810.2 and stable 52.0.2743.82 - Observed the output as shown in the screenshot

Firefox also displayed the same

Could you please provide a screenshot for further investigation on this.
Screen Shot 2016-07-29 at 2.40.58 PM.png
462 KB View Download

Comment 2 by brian.ch...@gmail.com, Jul 29 2016 

Sure, here's the screenshot, taken in Mac 10.11.6, Chrome 54.0.2810.2. I just upgraded to 54.0.2811.0 and saw the same results. I disabled all my extensions.

There was a very brief flash of correct content before it went blank.
svg-screenshot.png
71.4 KB View Download

Comment 3 by tkent@chromium.org, Aug 5 2016

Components: -Blink Blink>SVG

Comment 4 by f...@opera.com, Aug 5 2016 

Could you attach the contents of chrome://gpu ? Ppotentially also do a quick comparison of it between Chrome 52 and 54.)

Comment 5 by brian.ch...@gmail.com, Aug 5 2016 

Sure. See attached.
gpu-chrome-52.pdf
3.9 MB Download
gpu-chrome-54.pdf
311 KB Download

Comment 6 by f...@opera.com, Aug 5 2016 

Thanks! The things that stands out is that "Rasterization" is hardware accelerated in 54, but not in 52. Could you try disabling "GPU rasterization" in 54 (chrome://flags/#enable-gpu-rasterization or so), and see if the issue still reproduces?

Comment 7 by brian.ch...@gmail.com, Aug 5 2016 

Yup, that did it. If I disable GPU rasterization, the SVG shows up just fine. When I turn it back on, it's blank again.

Comment 8 by f...@opera.com, Aug 5 2016

Cc: erikc...@chromium.org ccameron@chromium.org
Summary: Page does not display with embedded SVG when GPU rasterization is enabled (was: Page does not display with embedded SVG)
Thanks for confirming.

Comment 9 by schenney@chromium.org, Aug 5 2016

Components: Internals>GPU>Rasterization
Labels: -Needs-Feedback
Status: Untriaged (was: Unconfirmed)
GPU team, any idea what might be causing this?

Comment 10 by ericrk@chromium.org, Aug 8 2016

Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
Not getting a repro locally, but may be due to a specific GPU - I'll keep investigating.

In the meantime, are you able to confirm whether this reproduces on Chrome 52 if you set "GPU rasterization" to "force enabled for all layers" in about:flags? (or by passing --force-enable-gpu-rasterization on the cmd line).

Thanks very much!

Comment 11 by brian.ch...@gmail.com, Aug 8 2016 

With GPU rasterization set to "force enabled...", the SVG renders just fine in Chrome 52.0.2743.116 (64-bit).

Comment 12 by ericrk@chromium.org, Aug 8 2016

Mergedinto: 633659
Status: Duplicate (was: Assigned)
From looking at about://gpu, it appears that you are running with "--enable-unsafe-es3-apis". There is another bug,  crbug.com/633659 , which causes us to fail rendering when using MSAA with gpu raster and "--enable-unsafe-es3-apis".

I've confirmed that this is the same issue and the fix (pending, in CQ) for that issue will address this as well.
►

Sign in to add a comment