Model Name:	MacBook Pro
  Model Identifier:	MacBookPro14,3
  Processor Name:	Intel Core i7
  Processor Speed:	2.9 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	8 MB
  Memory:	16 GB
  Boot ROM Version:	MBP143.0178.B00
  SMC Version (system):	2.45f0
  Serial Number (system):	C02WM9DJHTD6
  Hardware UUID:	AEDB4678-61FB-56E9-9DB3-8CE0A39B732D

Thanks for the report. Can you attach a screen capture showing what you mean?

The problem went away by itself.  I used Firefox for the rest of the day, and this morning started chrome again and it works fine and performs smoothly.  

When I was updating the chrome version, I had dozens of tabs in 4 different profiles.  Perhaps there is some background one-time post-update processthat did not play well with so many profiles and tabs?  Anyways, it is ok now, your call whether you want to close this or continue looking into it as a post update issue.

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

Steps to try and recreate: load a macbook pro with the previous version, create 4 profiles with 20 tabs each, set chrome to use existin tabs on startup, and run he version update to 69.

Oh, and needless to say if you need more information on my configuration (like which extensions I have) I will be happy to help.

TE, can you see if you can repro this? It sounds like the upgrade step may be required; see #6.

Unable to reproduce the issue on chrome reported version# 69.0.3497.100 using Mac 10.13.6 with steps mentioned below:
1) Launched chrome version(#68.0.3440.106) and created four profiles with 20 tabs opened in each profile
2) In chrome://settings, checked the "Open a specific page or set of pages" under "On startup"
3) Updated the chrome to M-69 form Chrome://settings/help, chrome got updated to 69.0.3497.100
4) Navigated to all the profiles and started browsing, able to browser normally.

@Reporter: Please find the attached screencast for your reference and let us know if we missed anyhtinh in reproducing the issue, provide your feedback on it which help in further triaging it in better way.

Thanks!

Deleted: 889585.mp4 9.2 MB

	889585.mp4 9.2 MB View Download

Ah!  I nailed it!  Steps to reproduce:

1) Install google-hangouts on your mac
$ brew cask install google-hangouts

2) Start the browser - it will work fine.

3) Start the handgouts app.  Chrome is brought to its knees.

4) Quit the hoangouts app.  Chrome is back to normal.

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

#10: Okay, I think I reproduced this issue by doing these steps (to avoid using Homebrew):

1) Download & install <https://dl.google.com/googletalk/googletalkplugin/GoogleVoiceAndVideoSetup.dmg> (note that this thing is extremely extremely deprecated, as far as I can tell)
2) Install the hangouts extension from <https://chrome.google.com/webstore/detail/google-hangouts/nckgahadagoaajjgafhacjanaoiihapd> (also deprecated)
3) Use Chrome normally
4) Start the Hangouts extension's UI
5) Watch everything start being extremely slow/janky

I took a sample of Chrome while in the slow/janky state but unfortunately there is nothing useful there - it seems pretty clear that this is an IPC message flood caused by the Hangouts app but I'm not sure how to debug those. The browser process shows 20-25% cpu use in Chrome's task manager when doing anything in this state, but samples show little actual work being done.

Symbolized sample attached.

Deleted: hangouts-hang.txt 175 KB

hangouts-hang.txt 175 KB View Download

Curious: why are you avoiding homebrew?

#13: I didn't want to figure out how to configure it on my corporate machine to reproduce this bug.

sagel@, can you help? I don't know how to debug the hangouts plugin at all and groby@ says you might have advice :)

Sorry, I've been off of Hangouts for quite a while, but amyfreestone@ is still a little closer to that and may be able to help.

*** UI Mass Triage ***

Assigning back to ellyjones@ for finding an owner.

Adding appropriate labels.

I am working on getting in touch with amyfreestone@.