Issue metadata
Sign in to add a comment
|
SVG parse error on load for mobile only
Reported by
eurocom....@gmail.com,
Mar 9 2018
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Open latest chrome version on Android phone! 2. Navigate to any .svg file (ex. https://it.vertigovape.eu/gfx/vertigo.svg) 3. You will get error, and below is rendering page up to first error. What is the expected behavior? Normally displayed svg. What went wrong? I realised that my svg contains 3 shapes, the error occours on second. So it stops rendering complete image. I went into the same issue on other sites, that I think contains multi shape svgs. Now I know that my svg is exported from photoshop, that can cause the problem, but the point is that, two days earlier everything worked fine, and everything works still fine in Windows Chrome, and Samsung mobile browser, and Android Firefox Beta. I already checked with system admin if any modifications or upgrades were made on server, and he confirmed that there were no modifications or upgrades on server. The really strange thing is that, if you continue to refresh the page several times, sometimes the image is displayed correctly with no errors, so it makes me feel that this is a latest update bug. Attaching some screenshots. Did this work before? Yes Previous to this update. Does this work in other browsers? Yes Chrome version: 65.0.3325.109 Channel: n/a OS Version: 6.0.1 Flash Version: I think that svg XML is parsed correctly for first shape, but as soon that it passes to next one it crashes. If you continue to refresh sometimes it shows up good. I cleared the cash to be sure. Here's an image: https://it.vertigovape.eu/gfx/vertigo.svg
,
Mar 12 2018
,
Mar 13 2018
Tested the issue in Android and could not reproduce the issue. Steps Followed: 1. Launched Browser 2. Navigated to https://it.vertigovape.eu/gfx/vertigo.svg 3. Observed the image loading Chrome Versions tested: 65.0.3325.109 Android Version: Samsung S7: 6.0.1 @eurocom: Could you please help us with details of your device for further triaging. Thanks!!
,
Mar 13 2018
Sorry I already changed the image. Ill mail you laiter an original image. Il 13 Mar 2018 11:40 AM, "sandeepk… via monorail" < monorail+v2.1342645230@chromium.org> ha scritto:
,
Mar 13 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2018
Waiting on the original SVG promised in comment #4. Thanks.
,
Mar 13 2018
Here's an old version. Like I said try refreshing several times. Sometimes it's parsed ok. https://it.vertigovape.eu/gfx/vertigo_old.svg Reexported with illustrator as single shape, works fine!
,
Mar 13 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2018
Reproduces in Canary on a Pixel 2 and an old Nexus 5 in 65.0.3325.109. probably also broken in 66. Adding labels as such. Can we bisect on Android? I think the most likely breaking change is not in SVG but in the XML parser or the loader.
,
Mar 13 2018
I also thimk this is xml issue.
,
Mar 13 2018
Note that this is an SVG document consisting entirely of <image> tags with base64 encoded png images.
,
Mar 13 2018
Let me know if you need any help!
,
Mar 13 2018
This image is not a truly vector image as I said before, it is exported as shape from photoshop, its really not the point. I agree that svgs shoul be made properly, but the point is, tha it worked fine on previous version, and it works flawlessly in other browsers.
,
Mar 13 2018
Check this URL with same parameters: https://eu.battle.net/forums/en/wow/topic/1840304591
,
Mar 13 2018
Sometimes you get crappy battlenet page.
,
Mar 13 2018
Oh I think in that place are some fonts on battlenet.
,
Mar 13 2018
Looks like there are several similar (or the same) cases being filed, I know of issue 812148 and issue 820163 . A quick search just now found issue 821333 . None of those appear to be "Mobile-only" though. One commonality that I see though is that the files are > 64k and have (or, rather, will have internally) different encodings in different blocks (first UTF-16 and then Latin1.) In this case there appear to be a BOM within the metadata block at the start (the xpacket PI.)
,
Mar 16 2018
,
Mar 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4be2115e0abf80619cbf702d0619520d0c4c868d commit 4be2115e0abf80619cbf702d0619520d0c4c868d Author: Stephen Chenney <schenney@chromium.org> Date: Fri Mar 16 18:30:55 2018 Revert "Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c" This reverts commit c0a946a4dec56ce5906a78f6e0b0c1f9e12c70b6. Reason for revert: Breaks content all over the web. Bug: 820163 , 822673 , 820561 , 812148 , 821333 Original change's description: > Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c > > This fixes a number of bugs found on clusterfuzz. > > Change-Id: Id2fa1d96e55be1e0483c135c20c20b90a068f4c3 > Bug: 790944 > Bug: 793715 > Bug: 796804 > Bug: 799707 > Reviewed-on: https://chromium-review.googlesource.com/897220 > Commit-Queue: Joel Hockey <joelhockey@chromium.org> > Reviewed-by: Scott Graham <scottmg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533953} TBR=dcheng@chromium.org,scottmg@chromium.org,joelhockey@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 790944 , 793715 , 796804 , 799707 Change-Id: Ic6b934d384229b9cf9092d559b865bbe8f278f38 Reviewed-on: https://chromium-review.googlesource.com/966684 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Commit-Position: refs/heads/master@{#543766} [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/README.chromium [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/chromium/chromium-issue-628581.patch [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/linux/xml2-config [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/HTMLparser.c [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/configure.ac [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/libxml2.spec [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/parser.c [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/parserInternals.c [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/win32/Makefile.msvc [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/win32/configure.js [delete] https://crrev.com/431c6dbf0a42d0c31c7dccd6553c6c496f1042a0/third_party/libxml/src/win32/libxml2.rc [modify] https://crrev.com/4be2115e0abf80619cbf702d0619520d0c4c868d/third_party/libxml/src/xmlIO.c
,
Mar 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0f92ca1175c89aec344326778c755ba57ef4d314 commit 0f92ca1175c89aec344326778c755ba57ef4d314 Author: Stephen Chenney <schenney@chromium.org> Date: Fri Mar 16 18:50:19 2018 Revert "Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c" M-65 stable merge. This reverts commit c0a946a4dec56ce5906a78f6e0b0c1f9e12c70b6. Reason for revert: Breaks content all over the web. Bug: 820163 , 822673 , 820561 , 812148 , 821333 Original change's description: > Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c > > This fixes a number of bugs found on clusterfuzz. > > Change-Id: Id2fa1d96e55be1e0483c135c20c20b90a068f4c3 > Bug: 790944 > Bug: 793715 > Bug: 796804 > Bug: 799707 > Reviewed-on: https://chromium-review.googlesource.com/897220 > Commit-Queue: Joel Hockey <joelhockey@chromium.org> > Reviewed-by: Scott Graham <scottmg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533953} TBR=dcheng@chromium.org,scottmg@chromium.org,joelhockey@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 790944 , 793715 , 796804 , 799707 Change-Id: Ic6b934d384229b9cf9092d559b865bbe8f278f38 Reviewed-on: https://chromium-review.googlesource.com/966684 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#543766}(cherry picked from commit 4be2115e0abf80619cbf702d0619520d0c4c868d) Reviewed-on: https://chromium-review.googlesource.com/967021 Cr-Commit-Position: refs/branch-heads/3325@{#714} Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369} [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/README.chromium [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/chromium/chromium-issue-628581.patch [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/linux/xml2-config [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/HTMLparser.c [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/configure.ac [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/libxml2.spec [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/parser.c [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/parserInternals.c [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/win32/Makefile.msvc [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/win32/configure.js [delete] https://crrev.com/483290671a61fdd75600a7b7f5e4a940ba814e9b/third_party/libxml/src/win32/libxml2.rc [modify] https://crrev.com/0f92ca1175c89aec344326778c755ba57ef4d314/third_party/libxml/src/xmlIO.c
,
Mar 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/54a1c705833b375b124b014159dcadda02a80e9b commit 54a1c705833b375b124b014159dcadda02a80e9b Author: Stephen Chenney <schenney@chromium.org> Date: Fri Mar 16 19:00:42 2018 Revert "Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c" This reverts commit c0a946a4dec56ce5906a78f6e0b0c1f9e12c70b6. M-66 merge. Reason for revert: Breaks content all over the web. Bug: 820163 , 822673 , 820561 , 812148 , 821333 Original change's description: > Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c > > This fixes a number of bugs found on clusterfuzz. > > Change-Id: Id2fa1d96e55be1e0483c135c20c20b90a068f4c3 > Bug: 790944 > Bug: 793715 > Bug: 796804 > Bug: 799707 > Reviewed-on: https://chromium-review.googlesource.com/897220 > Commit-Queue: Joel Hockey <joelhockey@chromium.org> > Reviewed-by: Scott Graham <scottmg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533953} TBR=dcheng@chromium.org,scottmg@chromium.org,joelhockey@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 790944 , 793715 , 796804 , 799707 Change-Id: Ic6b934d384229b9cf9092d559b865bbe8f278f38 Reviewed-on: https://chromium-review.googlesource.com/966684 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#543766}(cherry picked from commit 4be2115e0abf80619cbf702d0619520d0c4c868d) Reviewed-on: https://chromium-review.googlesource.com/966962 Cr-Commit-Position: refs/branch-heads/3359@{#288} Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276} [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/README.chromium [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/chromium/chromium-issue-628581.patch [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/linux/xml2-config [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/HTMLparser.c [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/configure.ac [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/libxml2.spec [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/parser.c [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/parserInternals.c [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/win32/Makefile.msvc [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/win32/configure.js [delete] https://crrev.com/11b924f8c4a7c84bfb46e8df78e7ef8d330dc907/third_party/libxml/src/win32/libxml2.rc [modify] https://crrev.com/54a1c705833b375b124b014159dcadda02a80e9b/third_party/libxml/src/xmlIO.c
,
Mar 16 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d8901956103e21b8c3461b779e99cd5d7f50f3ad commit d8901956103e21b8c3461b779e99cd5d7f50f3ad Author: Stephen Chenney <schenney@chromium.org> Date: Fri Mar 16 19:19:12 2018 Revert "Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c" This reverts commit c0a946a4dec56ce5906a78f6e0b0c1f9e12c70b6. Canary build branch merge. Reason for revert: Breaks content all over the web. Bug: 820163 , 822673 , 820561 , 812148 , 821333 Original change's description: > Roll libxml to 707ad080e61014ab4a6d60dc12875e233c1f673c > > This fixes a number of bugs found on clusterfuzz. > > Change-Id: Id2fa1d96e55be1e0483c135c20c20b90a068f4c3 > Bug: 790944 > Bug: 793715 > Bug: 796804 > Bug: 799707 > Reviewed-on: https://chromium-review.googlesource.com/897220 > Commit-Queue: Joel Hockey <joelhockey@chromium.org> > Reviewed-by: Scott Graham <scottmg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533953} TBR=dcheng@chromium.org,scottmg@chromium.org,joelhockey@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 790944 , 793715 , 796804 , 799707 Change-Id: Ic6b934d384229b9cf9092d559b865bbe8f278f38 Reviewed-on: https://chromium-review.googlesource.com/966684 Reviewed-by: Daniel Cheng <dcheng@chromium.org> Reviewed-by: Stephen Chenney <schenney@chromium.org> Commit-Queue: Stephen Chenney <schenney@chromium.org> Cr-Original-Commit-Position: refs/heads/master@{#543766}(cherry picked from commit 4be2115e0abf80619cbf702d0619520d0c4c868d) Reviewed-on: https://chromium-review.googlesource.com/966690 Cr-Commit-Position: refs/branch-heads/3372@{#1} Cr-Branched-From: ad7f48548867b059f459e13c53bb8e2e96027381-refs/heads/master@{#543592} [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/README.chromium [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/chromium/chromium-issue-628581.patch [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/linux/xml2-config [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/HTMLparser.c [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/configure.ac [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/libxml2.spec [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/parser.c [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/parserInternals.c [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/win32/Makefile.msvc [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/win32/configure.js [delete] https://crrev.com/ad7f48548867b059f459e13c53bb8e2e96027381/third_party/libxml/src/win32/libxml2.rc [modify] https://crrev.com/d8901956103e21b8c3461b779e99cd5d7f50f3ad/third_party/libxml/src/xmlIO.c |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by eurocom....@gmail.com
, Mar 10 2018