-
Notifications
You must be signed in to change notification settings - Fork 186
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
chromium-ozone-wayland 101 SVG issue #647
Comments
If I run chromium without --in-process-gpu, the SVG images display correctly (but no HW accel). Does SVG rendering use the GPU? Is there a flag to force software rendering of SVG images? |
More narrowly, if I run --in-process-gpu --disable-gpu-rasterization then SVGs display ok. So something in GPU rasterization in chromium 101 on i.MX8QM vivante GPU is causing problems for SVG image rendering. |
As far as I understand, this is a Chromium bug. |
Is this bug still present in newer versions of Chromium? |
We don't see this issue anymore on the NXP 5.15-based BSP. Even the older version of Chromium where the bug was present now works when running against the new 5.15, whereas it presented the bug on 5.4. |
I see the same behavior running Torizon OS 6.4.0+build.5 that is based on NXP 5.15 BSP. |
Upgraded from chromium 92 -> 101 on i.MX8QM using wayland, and most SVG files are not displaying (with no error messages in stderr or console). Did anything change recently in SVG handling? The same version of x86 chromium run on my laptop (with wayland) displays the SVGs correctly.
The text was updated successfully, but these errors were encountered: