Note, I guess the flash version is from the Firefox browser that I used to report the issue. ;-)

Attaching the stack trace after signal 11.

Deleted: chromium-crash.txt 1.5 KB

chromium-crash.txt 1.5 KB View Download

Further bits of information: when the browser is in that state, restarting the browser does not help.  Every time the same behavior emerges and no tab is usable.  It only goes away after rebooting the machine.

Maybe "the whole browser" is a better choice for "How much crashed?" because there is just one stack trace shown in console yet all tabs are affected.

The phenomenon shows fairly often but not every single time when I boot and log in.  For example, this comment is written from a functioning Chromium after logging in quickly and starting Chromium immediately after login.

I just notice there are desktop notifications for each extension mentioning that it crashed.

shortcutter@ could you help us with the server ID from the "chrome://crashes" for further triage.

Thank You...

Unfortunately crash reporting is switched off, says Chromium.  I do not have apport installed.  Is that what I should do or is there anything else that I should to do enable crash reporting?

Thank you for providing more feedback. Adding requester "kkaluri@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

Unable to reproduce the issue on Ubuntu 16.04 using chrome reported version-56.0.2924.76, stable & latest dev version as per the below steps:
1.Boot ubuntu machine.
2.Launch chromium
3.All the tabs content loaded properly without any issue & No crash observed.

Please check the issue by upgrading to the latest versions(M58 / M60 builds-60.0.3083.0) of chromium & let us know your observations on the same.
Thank you..!!

Since comment 9 I could only observe one such crash today.  I had 58.0.3029.81-0ubuntu0.16.04.1277 since 2017-04-27 and 58.0.3029.96-0ubuntu0.16.04.1279 since 2017-05-10.

Interestingly two of the four tabs crashed:
https://mail.google.com/mail/u/0/#inbox
https://www.buzzfeed.com/sheerafrenkel/google-has-a-secret-team-making-sure-its-products-are-safe?utm_term=.nf4qD629P#.hgaJ3WVB5

But not the two on https://forum.ubuntuusers.de/

Another observation: GMail tab loads and displays content and only after a few seconds (JavaScript loaded?) the tab crashes.

Deleted: ch-crash-2017-05-12.txt 2.8 KB

ch-crash-2017-05-12.txt 2.8 KB View Download

Thank you for providing more feedback. Adding requester "jmukthavaram@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

Attaching stacks of the two crashed tabs with URLs.  I am assuming there is an unfortunate interaction with the graphics driver or hardware.  Also attaching output of "lshw" in case that is helpful.

Deleted: chromium-stacks-2017-05-13.txt 7.0 KB

chromium-stacks-2017-05-13.txt 7.0 KB View Download

Deleted: hw.txt.gz 4.0 KB

hw.txt.gz 4.0 KB Download

Based on Stack provided in C#10 and C#11, seeing many layout related changes, hence adding the component accordingly for more inputs from someone of the respective team.

Crash in SVG transforms code. 

I'm having a very hard time understanding how this could be a Blink bug if the problem persists after a browser restart, and can only be cleared by a machine restart. Blink, to my knowledge, just does not have the privileges to do something that would affect a machine that way.

I'm guessing the Chromium is starting up before some graphics driver, or other functionality, is fully initialized, and that is corrupting the machine.

Is this a local build of Chromium?

Assigning to the GPU team in the event they have some knowledge on this. Otherwise I think we need to close this as WontFix.

> I'm guessing the Chromium is starting up before some graphics driver, or other functionality, is fully initialized, and that is corrupting the machine.

So far Chromium ist the only program that exhibits this behavior.  While I have to agree on the first speculation, I think we cannot say the machine or even complete DE session is affected, because so far only Chromium exhibits the behavior.

> Is this a local build of Chromium?

It is the version (or rather several versions) from the official Ubuntu package repository (16.04 LTS, 64 bit).

Please report bugs in ubuntu-packaged chromium-browser builds to ubuntu (https://help.ubuntu.com/community/ReportingBugs). They always add local patches that may change behavior in various ways.