Unable to reproduce the issue on Chrome stable version 59.0.3071.115 on Ubuntu 14.04. Navigated to the provided URL and no crashes were observed.

@ acquadoria: Request you to please update chrome to the latest stable available and try again. Please update us with your observations.

P.S: Please also help us with a crash ID generated from chrome://crashes if issue replicates again.

Thanks.!

I got this problem using Debian Jessie. I opened another issue to
Debian with more informations.https://bugs.debian.org/cgi-bin/bugreport
.cgi?bug=865592

Le jeudi 29 juin 2017 à 05:08 -0700, ranjit… via monorail a écrit :

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

??? I do not find how to enable Crash reporting? ???
??? Console warning may be a track ???

1) Not Debian Jessie, but Stretch

2) chrome://crashes/
gives:
[
Crash reporting is disabled.
Crash reporting is not available in Chromium.
]

3) Console gives a Warning
[
Resource interpreted as Document but transferred with MIME type application/xml: "http://pecita.net/".
]
Also, tab network:
[
*General*
Request URL:http://pecita.net/
Request Method:GET
Status Code:200 OK
Remote Address:51.15.139.217:80
Referrer Policy:no-referrer-when-downgrade
*Response Headers*
Accept-Ranges:bytes
Connection:Keep-Alive
Content-Encoding:gzip
Content-Length:868
Content-Type:application/xml
Date:Fri, 30 Jun 2017 13:24:45 GMT
ETag:"bd8-54f267f3dc589-gzip"
Keep-Alive:timeout=5, max=100
Last-Modified:Wed, 10 May 2017 07:34:05 GMT
Server:Apache/2.4.18 (Ubuntu)
Vary:Accept-Encoding
*Request Headers*
Provisional headers are shown
Upgrade-Insecure-Requests:1
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
]
Also:
*General*
Request URL:http://pecita.net/s/toc.xsl
Referrer Policy:no-referrer-when-downgrade
*Request Headers*
Provisional headers are shown
Accept:text/xml, application/xml, application/xhtml+xml, text/xsl, application/rss+xml, application/atom+xml
Referer:http://pecita.net/
User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36

4) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865592

Please refer the below link to enable crash reporting on chrome:

https://support.google.com/chrome/answer/96817?co=GENIE.Platform%3DDesktop&hl=en

Thanks.!

Of course I saw this link but it is helpless!
[Automatically send usage statistics and crash reports to Google]
does not exist
That exist is
[Automatically report details of possible security incidents to Google]
But it's turned on and does not cause any effect for this issue...

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi there,

Can you please navigate to chrome://settings --> Click on Advanced option and under Privacy and security check for "Automatically send usage statistics and crash reports to Google" . It should be present. Please try enabling it. Attached is a screen shot to  give you an idea about it.

Thanks.!

Deleted: Settings.png 240 KB

	Settings.png 240 KB View Download

Not this page:...

Deleted: Capture du 2017-07-04 12-23-28.png 77.7 KB

	Capture du 2017-07-04 12-23-28.png 77.7 KB View Download

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Dear developer,
The problem persists. Can we move it forward?

Can you please update your system to the latest stable available and let us know if the issue still persists.

Thanks.!

Hello.
The problem does not persist with the latest stable version, it happens!
The complete system informations are given by the link:
4) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865592

Here an inline copy:

Package: chromium
Version: 59.0.3071.86-1
Severity: normal

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  libasound2           1.1.3-5
ii  libatk1.0-0          2.22.0-1
ii  libavcodec57         7:3.2.5-1
ii  libavformat57        7:3.2.5-1
ii  libavutil55          7:3.2.5-1
ii  libc6                2.24-11+deb9u1
ii  libcairo2            1.14.8-1
ii  libcups2             2.2.1-8
ii  libdbus-1-3          1.10.18-1
ii  libdrm2              2.4.74-1
ii  libevent-2.0-5       2.0.21-stable-3
ii  libexpat1            2.2.0-2+deb9u1
ii  libflac8             1.3.2-1
ii  libfontconfig1       2.11.0-6.7+b1
ii  libfreetype6         2.6.3-3.2
ii  libgcc1              1:6.3.0-18
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0         2.50.3-2
ii  libgtk2.0-0          2.24.31-2
ii  libharfbuzz0b        1.4.2-1
ii  libicu57             57.1-6
ii  libjpeg62-turbo      1:1.5.1-2
ii  libminizip1          1.1-8+b1
ii  libnspr4             2:4.12-6
ii  libnss3              2:3.26.2-1.1
ii  libpango-1.0-0       1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpng16-16          1.6.28-1
ii  libpulse0            10.0-1+deb9u1
ii  libre2-3             20170101+dfsg-1
ii  libsnappy1v5         1.1.3-3
ii  libstdc++6           6.3.0-18
ii  libvpx4              1.6.1-3
ii  libwebp6             0.5.2-1
ii  libwebpdemux2        0.5.2-1
ii  libx11-6             2:1.6.4-3
ii  libx11-xcb1          2:1.6.4-3
ii  libxcb1              1.12-1
ii  libxcomposite1       1:0.4.4-2
ii  libxcursor1          1:1.1.14-1+b4
ii  libxdamage1          1:1.1.4-2+b3
ii  libxext6             2:1.3.3-1+b2
ii  libxfixes3           1:5.0.3-1
ii  libxi6               2:1.7.9-1
ii  libxml2              2.9.4+dfsg1-2.2
ii  libxrandr2           2:1.5.1-1
ii  libxrender1          1:0.9.10-1
ii  libxslt1.1           1.1.29-2.1
ii  libxss1              1:1.2.2-1
ii  libxtst6             2:1.2.3-1
ii  x11-utils            7.7+3+b1
ii  xdg-utils            1.1.1-1
ii  zlib1g               1:1.2.8.dfsg-5

Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Could you test on Debian Strech?

I tried Chromium V60: I got the same problem.
Still unable to find the enabling dump option.
Piece of syslog attached...

Deleted: syslog_xmlAwSnap.txt 14.9 KB

syslog_xmlAwSnap.txt 14.9 KB View Download

Idem with chromium-browser 61.0.3163.100-1~deb9u1 (clearing cache and resetting settings)

Reporter@: Tested this issue on Debian 8.x using the chrome version #59.0.3071.86, #61.0.3163.100, #63.0.3233.0 and unable to reproduce the issue.

Attaching the screenshot for your reference.
Thank you!

Deleted: 736026.jpg 2.7 MB

	736026.jpg 2.7 MB View Download

Can someone from GPU dev team kindly look into this issue.

Thanks!

I will try to reproduce.

Reporter, can you go to about:gpu and attach the output to this bug?

> The problem does not persist with the latest stable version, it happens!

I wasn't clear what this means, did the problem resolve? But in chrome 60 it returned?

If I can't reproduce and we don't have a crash Id it will be very hard to do any action here though.

Thank You Dana.
1) about:gpu attached
2) From the moment I got the problem it persisted.
3) The other problem is that I do not know how to take a dump with Chromium under Debian 9: how to advance on this point?

Deleted: gpu.html 60.5 KB

gpu.html 60.5 KB View Download

Thanks, that confirms you're using gpu compositing. I tried to reproduce again on a linux chromium build with gpu compositing enabled, and am not able to do so.

> 3) The other problem is that I do not know how to take a dump with Chromium under Debian 9: how to advance on this point?


I might be wrong but I think "chromium" builds will not report crashes to google, whereas "chrome" will. Would you be able to try reproduce on an official chrome build?

I installed Chrome Version 61.0.3163.100 (Build officiel) (64 bits).
The problem does not occur.

P.S.
about:gpu with Chrome

Deleted: gpu.html 62.5 KB

gpu.html 62.5 KB View Download

Hrm, that's unfortunate, and I can't reproduce in a chromium build.

I looked at your syslog output and saw that the crash is in our XML code.

Aug  6 14:48:47 pecita05 chromium.desktop[5216]: [130:130:0806/144847.320756:FATAL:XMLDocumentParser.cpp(596)] Check failed: !IsLibxmlDefaultCatalogFile(url).

That check has this comment:

  // libxml should not be configured with catalogs enabled, so it
  // should not be asking to load default catalogs.
  CHECK(!IsLibxmlDefaultCatalogFile(url));

So it sounds to me like chrome is being build and static linked with a good libxml, but the one your chromium build is using has catalogs enabled and that is a problem.

I'm not sure how this got triaged to Internals>GPU actually.

The shouldAllowExternalLoad() function has a lot of authors no longer on the project, but I see a few familiar faces. Assigned to them to provide any more info if it exists or if we have anything we could do here.

This was changed from an early-exit to a CHECK in https://chromium.googlesource.com/chromium/src/+/519ead74e98302eabc1144ed9947e14d93adae95 . The author of that change (dominicc) is gone, but the reviewer (dcheng) is still here.

dcheng, any thoughts on this?

Same error message and "Aw, Snap!" page on Arch Linux, seems to be happening with builds that use the system libxml instead of the bundled one. Looks like you nailed it in comment 27, now all we need is a fix. :P

Should be resolved by: https://chromium-review.googlesource.com/1103710

Sorry for missing this bug when it was first filed. =(