Tentatively marking as SiteIsolation as out-of-process iframes are involved.

Thanks for the report!  A few questions to help us understand more:

1) Can you clarify which extension you're using?  There are separate ones for the Hangouts Extension (nckgahadagoaajjgafhacjanaoiihapd) and the Hangouts App (knipolnnllmklapflnccelgolnpehhpl).  You should be able to check on chrome://extensions.

2) As comment 2 notes, there's currently a Site Isolation field trial on Chrome Beta, which explains the Subframe process you see in Chrome's task manager.  Can you try disabling it (using the "Site isolation trial opt-out" at chrome://flags/#site-isolation-trial-opt-out) to see if the problem goes away?  Please let us know either way, so we can track down the problem.  There's more context at https://www.chromium.org/Home/chromium-security/site-isolation.

Thanks!

Sure, I will provide anything that I can.
1) Google Hangouts, 2018.123.418.2, ID: nckgahadagoaajjgafhacjanaoiihapd
This is the extension, not the app. I did use the app prior, but it is currently not installed (removed from Chrome).
2) I have set it to opt-out (not recommended).

I will report any changes, or no changes, after a full restart to ensure change has taken.

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

I can confirm that the step outlined for opt out of / disabling "Site Isolation field trial" does not change anything. This is after full reboot.

Interesting!  Just to confirm, when you opt out, you don't see any "Subframe: https://google.com/" processes anymore, right?

If so, I think we can exclude Site Isolation as the cause of this.

lukasza@: Do you know any Hangouts folks we could CC on this bug to investigate it from their side?

Incorrect, I still see the Subframe.... I was expecting to no longer see this per the description here, but it is still there. Here is a screenshot of Chrome with the setting as you requested, Since setting this, I have rebooted a few times already and there is no change at all.

To confirm and be clear... while my setting is as shown in the attached image, I DO still see the "Subframe: https://google.com/".

Deleted: Selection_015.png 23.1 KB

	Selection_015.png 23.1 KB View Download

Here is an image of the Chrome Task Manager, showing what I describe.

Deleted: Selection_017.png 21.6 KB

	Selection_017.png 21.6 KB View Download

Adding some people maintaining Hangouts

Ok, re-adding the SiteIsolation component since we haven't actually confirmed the bug goes away without it.

It's possible you have Site Isolation enabled another way, such as enterprise policy (visible in chrome://policy as SitePerProcess or IsolateOrigins) or via chrome://flags#enable-site-per-process.  That would explain why the trial opt-out didn't take effect.

Someone on our side should take a look to see if we can repro this locally in a clean profile (with and without Site Isolation).

I'd guess that the google.com subframe on the Hangouts extension is showing up due to --isolate-extensions, which has been shipped for a long time and can't be disabled.

If you double-click on the "Subframe: https://google.com" row, what gets focused?

Oh, good point!  I've been thinking too much about the more recent Site Isolation work and missed the obvious extension aspect.

If I double click the subframe entry in Chrome Task Manager, as requested, my browser comes to focus and opens a NEW tab with the following:
chrome://extensions/?id=nckgahadagoaajjgafhacjanaoiihapd
Which then displays the info for Google Hangouts extension.

The the other quesry, chrome://flags/#enable-site-per-process, which is titled "Strict site isolation" is currently disabled. I did not change this settings, it was and still is disabled.

Is it possible to get a performance trace of the offending window using Chrome Dev Tools (or anything more appropriate as deemed by the Chrome folks)?

Sure, but I will need a bit more clarification. What is the "offending window" and could you outline exactly how you would like it done. I have been asked and done a few types of traces so I want to be sure to get you exactly what you are asking for. Additionally, there really is no "window" that is an issue. I can have no windows open, or windows open.

If I am misunderstanding anything, please do just help me understand and I will do my best to get you what is needed.

Wanted to check since it has been a while... are you waiting on anything from me?

I have removed Hangouts and can confirm that there is no longer an issue. IF there is no fix, and Chrome is mishandling the extension with no way to change it (per the above), is there a different way to use Hangouts? I can switch over to Firefox for browser issues, but it still leaves Hangouts with no way to use it. The only real way to use these tools is to use Chrome, at least as far as I can see.

I also wanted to confirm the issue (with Hangouts installed and in use) with the latest system configuration. I am using Chrome Version 67.0.3396.18 (Official Build) beta (64-bit) and still on same OS, Ubuntu 18.04.

Thanks Brian! We've been able to repro locally and are investigating. I'll update this bug when we know more.

Brian, you can go to hangouts.google.com and I believe get all the same functionality as with the extension, albeit less conveniently.

Thanks for the message, I appreciate the suggestion to help my experience. I am aware of the web interface, as well as some third party attempts as a desktop client. I like the app/extension because I also have my SMS sent to it, so I can have it run in background and still get alerts from SMS.

I am looking at YakYak as a possibility, but it seems quite resource intensive when compared to the app/ext for Chrome, but I need to consider what it is. I tried using the extension for Thunderbird, but as I am sure you know, the functionality there has always been limited, and now, more not there than limited.

There is also no real option for Firefox, I thought to try that route as well. All the options I could find seem to be nothing but a wrapper of sorts around the web interface, which is what you have suggested here.

Unable to reproduce the issue on ubuntu 17.10 using chrome latest stable #66.0.3359.170 and latest dev #68.0.3423.2.

Attached a screen shot for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened Chrome by both enabling and disabling site isolation. 
2. Opened hangouts extension and left it running in background.
3. After some time, waited for 30 min.
4. Observed that hangouts did not cause any high CPU usage.

brianjzech@ - Could you please check the issue on latest dev #68.0.3423.2 by creating a new profile without any apps and extensions and please let us know if the issue still persists or not.

Thanks...!!

Deleted: 830141.png 679 KB

	830141.png 679 KB View Download

Well, I need to clarify only to provide the proper detail you want. You ask me to install the most recent dev, which for me is google-chrome-unstable, which matches the version number you specified. There will be no need to make a new profile as it will create one automatically. I use the beta, not unstable, so when I install it I will get a new user profile folder "google-chrome-unstable" vs it using the "google-chrome-beta" one I normally use.

I assume all I stated about is proper. Next, you ask for no apps and no extensions, but this will be testing ONLY the browser, which I assume will work. I assume this on the basis that the version I use, beta, works just fine without Hangouts. So, are you wanting reports with no extensions and apps, or are you wanting reports with no other extensions or apps other than Hangouts?

Additionally, if there is any other data you would like captured, let me know. Otherwise, I will just be watching for the excessive CPU utilization.

For reference, the version I am currently using is Version 67.0.3396.40 (Official Build) beta (64-bit) running on Ubuntu 18.04.

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

Re #24: Those steps are insufficient to repro the issue; the problem tends to only appear after the device has been running for some time, and I think likely requires a suspend/resume cycle or two, for example.

This is being tracked internally by b/67557690.

Moving from Unconfirmed to ExternalDependency, since this appears to be a Hangouts bug.

Re #24:
I can confirm that using unstable 68.0.3423.2, there is no issue with no apps and no extensions installed, and a newly created profile. I can also confirm that Hangouts does still cause the problem.

Also Re #27:
I can confirm this to be correct. Initially, I tried my best to estimate a procedure to recreate it. But as I test on this more, I do see that it does vary... things like a fresh boot, booted for x hours, etc. I am unsure exactly what was meant by "suspend/resume cycle", but I have noticed things I believe that may be in reference to... like if I use Hangouts and close it (still open in background), it is more likely to soon show this issue.

I am sorry I cannot provide a better 1, 2, 3 here it is process.

Hey Brian,

Sorry for late reply. This issue is fully resolved in b/68142155 already. We cherry picked the change into our prod build so it should be available to you in next day or two.

Thanks, that is great news. Is this an update to Chrome, Hangouts, or both? Are there versions I might watch for, and/or a certain channel for Chrome?

I am unable to utilize the "b/" links.

This is a Javascript code change so you only need to wait for it. I'll follow up here when the build hit production, after which you could restart your extension/app to get the change (not an update to app/extension) which will resolve it.