specifying --safe-plugins does not help; browser still seg faults.

Confirmed, same issue, same version, same OS. Beta version had the same issue.

I'm seeing this same issue on my home machine as well, ever since the latest update I took. It happens repeatedly on every startup, roughly 1 minute after startup. It appears to not matter how many or what tabs are open. Can run other repro steps if any Linux devs want to jump in.

Isn't flash unbundling targeting M54? waffles@, any thoughts here?

The crash from my home machine is visible here:

go/crash/e079ffae00000000

"Failed to locate and load the component updated flash plugin." is expected to show on Linux in certain circumstances¹, and is almost certainly a red herring (it should never cause a crash).

¹The message will show if there has been no component update to Flash applied yet. A component update to Flash is applied:
(a) after 6 minutes of the browser being up
(b) when Flash content is encountered
and will be written into the current user-data-dir.

I'm curious, though, what you see if you navigate to chrome://components.

Users experienced this crash on the following builds:

Linux Beta 53.0.2785.92 -  5.53 CPM, 14 reports, 10 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Does LinuxMint have a Chromium Browser package? If so, can you try that and see if it also crashes? 

Chromium for my Linux (LMDE) is Version 31.0.1650.63 Debian jessie/sid (238485). It does not appear to crash. I don't use it much, though, so I don't have any spiffy extensions/plugins installed. (nor that many under Chrome, fwiw.)

Huh, that's ancient. So it's not a useful comparsion. Why doesn't LMDE carry 53.x like Debian Jessie? https://packages.debian.org/jessie/chromium

I am lame and am not running the most recent LMDE. Unfortunately the upgrade/update to the latest is not advertised as "trivial".

Umm, ok. Never had trouble upgrading plain Ubuntu or Debian here.

So is this https://www.linuxmint.com/edition.php?id=102 ? When you "apt-get install" some new package, where are those .deb packages coming from?

My /etc/apt/sources.list.d/google-chrome.list has this line:
  deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main

I usually use either aptitude at the command line or the synaptic GUI. I really should do the update/upgrade of LMDE, but that's not happening for now.

Yes, I know where Chrome comes from. I'm trying to figure out where the rest of the distro comes from, since it's not plain Debian/Ubuntu.

Ah. Here's what I have in official-package-repositories.list:

deb http://packages.linuxmint.com/ debian main upstream import
deb http://debian.linuxmint.com/latest testing main contrib non-free
deb http://debian.linuxmint.com/latest/security testing/updates main contrib non-free
deb http://debian.linuxmint.com/latest/multimedia testing main non-free

Note that LMDE 1 is either barely on life-support or perhaps now officially deprecated. Like I said, I do need to upgrade, but it's not "debian easy", so I haven't gotten there yet.

Thanks, but still not helpful. The crash is in libglib-2.0.so.0.3600.4 and I haven't figure out where the package for that is.

http://debian.linuxmint.com/ is rejecting connections. I don't see any glib packages in http://packages.linuxmint.com/pool/main/ under g or l. It's not Debian's since they carry libglib-2.0.so.0.4200.1 in Jessie and libglib-2.0.so.0.3200.4 in Squeeze.

Well, I eventually found the right libglib2.0-0_2.36.4-1_amd64.deb that corresponds to what's installed on your system on a LinuxMint repo mirror.

And the crash inside libglib looks like this. No idea why it's crashing though.

0  libglib-2.0.so.0.3600.4!g_main_context_check [gmain.c : 3537 + 0x4]
1  libglib-2.0.so.0.3600.4!g_main_context_iterate [gmain.c : 3698 + 0x11]
2  libglib-2.0.so.0.3600.4!g_main_context_iteration [gmain.c : 3762 + 0x14]
3  chrome!base::MessagePumpGlib::Run [message_pump_glib.cc : 309 + 0x5]

I gave up and tried to do the update to LMDE 2. It sort of worked - ssh and VNC into the system was OK - but my X and/or video setup was hosed. Fell back to doing a full install of LMDE 2; fortunately I had configured a separate root partition, so my home files were spared.

Just installed the google-chrome-stable package: Version 53.0.2785.101 (64-bit)

It doesn't crash. It *does* exhibit some rendering artifacts in some tabs sometimes (how's that for a useless bug description?) that I have seen on a MacBook Pro running El Capitan. So much for "stable"; well, it is doing the same sort of thing at least. The browser seems to remember my settings (/home was left intact after all) but I have not explicitly (re)installed any of my plugins or extensions, so if there was anything tucked over in / it is no longer there to cause crashes.

If you have rendering artifacts, please file a separate bug.

So is the crash gone? It's hard to tell exactly what happened, as both Chrome and the OS got updated.

Users experienced this crash on the following builds:

Linux Dev 55.0.2853.0 -  3.25 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Beta 54.0.2840.16 -  4.39 CPM, 3 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

I am also experiencing this issue, on Chrome 54 Beta running on Ubuntu 16.04.

I am also experiencing this issue, on Chromium 53.0.2785.92 on Slackware Linux 14.1. I tested with different versions of glib2 as the segmentation fault seems to get triggered when calling something from that library, but it keeps segfaulting after about a minute.

re: comment 21 and comment 22. Without a crash report id for Chrome, or a backtrace for Chromium, it is impossible to tell if your problems are the same as this one. Observing a similar symptom does not imply the underlying cause is the same. Headaches can happen for a number of reasons. Crashing on startup can happen for a number of reasons.

The best course of action is to file your own bugs. Then we can investigate them separately to see if they are indeed this bug, or some other problem entirely.

Issue 649708 has been merged into this issue.

Issue 649708 was merged into this issue. I have a crash report id attached to it.

That issue happens when clicking on certain links in Chrome (seems to be related to target="_top"), for example:

* the "Contacts" Link @ gmail (in the drop-down @ top-left)
* the "Bootique" link @ http://blog.takipi.com/the-hitchhikers-guide-to-github-13-java-projects-you-should-try/

This is repeatable 100% of the time, on the latest Chrome 54 beta (54.0.2840.59 (Official Build) beta (64-bit)) including inside incognito windows, as well as with "--safe-plugins".

I cannot reproduce Issue 649708 (marked as a duplicate on this one) on Version 55.0.2883.21 beta (64-bit). At least that issue seems fixed.

Users experienced this crash on the following builds:

Linux Dev 56.0.2906.0 -  2.42 CPM, 2 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 57.0.2950.4 -  1.32 CPM, 11 reports, 6 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Issue 676291 has been merged into this issue.

Issue 686185 has been merged into this issue.

Users experienced this crash on the following builds:

Linux Dev 58.0.3004.3 -  0.20 CPM, 2 reports, 2 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 59.0.3047.0 -  0.69 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 60.0.3107.4 -  0.87 CPM, 2 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 61.0.3128.3 -  0.64 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Beta 62.0.3202.29 -  2.45 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 63.0.3239.9 -  0.95 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Beta 64.0.3282.85 -  0.69 CPM, 8 reports, 4 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 65.0.3322.3 -  0.61 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

 Issue 817083  has been merged into this issue.

Users experienced this crash on the following builds:

Linux Dev 66.0.3355.0 -  0.16 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Beta 65.0.3325.124 -  0.97 CPM, 6 reports, 2 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 66.0.3359.26 -  0.91 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Users experienced this crash on the following builds:

Linux Dev 67.0.3371.0 -  0.69 CPM, 1 reports, 1 clients (signature base::MessagePumpGlib::Run)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas

Issue 901503 has been merged into this issue.

Available, but no owner or component? Please find a component, as no one will ever find this without one.