Unable to reproduce the issue on 66.0.3359.117 using Ubuntu 14.04 and Ubuntu 17.10 with steps mentioned above. Launched chrome, navigated to amazon.com, fb.com , youtube -- used for sometime and closed chrome. Launched it again -- Didn't observe any "there was a problem loading your profile. Some feature might not work" error.

@Reporter: Does this happen only on signed in profile or with fresh profile which do not have any apps/extensions? Could you please check the issue on fresh profile and try below scenarios.

Scenario 1:
===========

1. Close all the chrome background process(if any)running in the background.
2. Relaunch browser and try to update.

Scenario 2
===========
1. Create a new browser user profile
2. Clear cache and cookies
3. chrome://settings- Reset Chrome browser settings
4. Update

If both the above scenarios doesn't work, uninstall and reinstall chrome(IMPORTANT: Make sure to backup your USER DATA folder) otherwise you will loose all the saved browser data.

Tentatively adding Internals>Installer label.

Thanks!

Do you see anything in chrome://crashes?

> Does this happen only on signed in profile or with fresh profile

I always use only one profile where I'm constantly signed in.
I have only 2 extensions, "Chrome UA Spoofer" (usually sitting there doing nothing), and "QR-code tag extension" (which just creates a QR code of the url you are navigating). I'm pretty sure they don't interfere in any way with the issue at hand.


> try below scenarios

Sorry but I'm not going to try anything involving creating fresh profiles, just too much work, and I'm definitely not going to reinstall chrome.

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

@Reporter: Could you please respond to comment#3. Hence adding Needs-Feedback label 

As issue is not reproducible for TE team removing Needs-Bisect label and adding UI>Browser>Profiles component. Could someone from dev team please have a look at this issue.

NOTE:  Issue 833446  looks similar to this issue. 

> Do you see anything in chrome://crashes?

I see a few items like this:
  Uploaded Crash Report ID 50f6fa500b214075 (Local Crash ID: Chrome)
  Crash report uploaded on Tuesday, December 5, 2017 at 12:57:34 PM
  Provide additional details

However, the latest is the one above from December 5, so definitely not from when I experienced the issue in the last days.

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

As we are unable to reproduce the issue from our end (..as per comment#2 and #6) adding label TE-NeedsTriageHelp and requesting some one from Dev team to have a look into this and help in further triaging it.

Thanks!

 Issue 833446  has been merged into this issue.

Can you please turn off "Continue running background apps when Google Chrome is closed" in chrome://settings/system and check whether this resolves your issues with reading profile?

--Chrome Identity automated triaging--

This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

> This bug is Unconfirmed and has gone two weeks without any activity, 
> so it is being closed as WontFix

This is fucking stupid. That the original reporter doesn't reply with the requested information within a given time span is no reason to close a bug where there's definitely enough information to be certain that there is a bug (which, by the way, means it shouldn't be "unconfirmed" in the first place).

> Can you please turn off "Continue running background apps when Google Chrome 
> is closed" in chrome://settings/system and check whether this resolves 
> your issues with reading profile?

That was already turned off, so no, it doesn't resolve the issue (and I hope you already realise that even if it did, that wouldn't be expected behavior).

> SYSTEMATICALLY, 100% OF THE FUCKING TIMES.

I must rectify that: it's not really 100% of the times, but almost.

It should go without saying but just in case: PLEASE REOPEN

Moving back to "Untriaged," since this is still being reproduced by the reporter. I don't think this is related to sign-in, so I'll let someone from the desktop team triage.

--Chrome Identity automated triaging--

This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity.

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

cc'ing some desktop folks for triaging

I think we need someone with Linux expertise to help out here. thestig: any ideas of what could be happening, or who might be good to investigate? Thanks.

+Tom because Linux

This bug is currently inactionable because we don't know *why* shutdown is being blocked.  We require more information.  +robliao (base/task_scheduler) is there any way of diagnosing what shutdown is blocked on?

It may be helpful to know what Linux distro this is on.

If you start with no chrome process running, and run:

google-chrome --enable-logging=stderr

from a terminal, use it for a while, and quit. Does the shell in the terminal get control back, or is chrome still running? If it's still running, what's the last 10 lines of logs in the terminal?

A dump of all of the thread stacks will answer this question most of the time. Is there a way we can get that?

Adding gab@ as well who is also interested in shutdown.

Try sending the chrome processes that are around SIGSEGV signals. i.e. kill -SEGV $pid. If Chrome is running from a terminal, it should print out the crash report IDs it uploaded. Or start Chrome again after that and check chrome://crashes for new crash IDs.