Does this only happen on wake from sleep (And not restart?)  Do you have mechanical storage?  That is, an HDD instead of an SSD - just wondering if there's a lot of paging going on (Due to a memory issue of some sort), which would be more pronounced with spinning disks.

It happens on both as far as I remember. In addition to that, I've just been doing other things on my pc for the past 2 hours, just opened up Chrome and it did this:
1 - Loaded up my popular pages, I clicked into about 6 of them and had them all open at once.
2 - Checked out about 3 of them.
3 - On the third page, none of the links were clickable.
4 - The 3 remaining pages didn't work.
5 - Closing Chrome was sluggish (clicked close and took about 5 seconds to close).
6 - Removed all Chrome tasks in Task Manager.
7 - Re-opened Chrome; sluggish start up. Opened up 3 remaining pages.
8 - Pages didn't load.
9 - Steps 5-7 were repeated.
10 - Finally works; on here reporting the problem.

This isn't the first time I've dealt with the issue mid-usage of my PC (as in, this also happens not just when I turn on my PC but it always happens in those cases).
Chrome is installed on my SSD; it always ran perfectly and very quickly up until a week ago.

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

Could you provide an about:profiler dump?  Next time this happens, wait until chrome is responsive again, then go to about:profile, and export the data.  This is very coarse grained data on how long tasks take (With no personally identifying information), recorded in the background when running Chrome.

What would be even better is an about:tracing trace.  To do this, you have to open up an about:tracing tab, select record (While the problem is ongoing) and then export the file (Select all options in the left column, none in the right).  Unfortunately, if Chrome is unresponsive, about:tracing may be unresponsive, too.  You can try to start a trace before you put your system to sleep, though I'm not sure how well that will work.

Also, before I give up on it being a memory issue (though it's not sounding like a leak), could you check how much memory you have free in task manager next time this happens?

Sorry, that "about:profile" should be "about:profiler".

I'm finding something very similar (Win10, Version 62.0.3202.94, 64-bit). What's interesting is that:

1. Microsoft Edge does not suffer the same hang
2. Firefox does not suffer the same hang
3. Opera DOES suffer the same hang

This is at least weakly suggestive that the issue could be with Google's WebKit.

Okay, in the morning Chrome was working fine. I even put it to sleep, woke it up and it worked perfectly okay. Then had to go out for an hour, had it on sleep and just woke it up to find out it was being problematic again.
I couldn't get tracing to run while it was doing the problem so I've got my profile dump (went on about:profile, took a few tries, and clicked save) so I'll attach whatever file I saved to this comment.

Seems like the problem isn't very consistent... maybe it needs to be on sleep for a longer while? Or something Windows does in the background at certain times of the day.

Unfortunately I forgot to check the memory usage BUT I did open up task manager to kill the tasks and didn't notice any large memory usage (no red/orange colours in the entire task manager). I will double check next time but it doesn't look to be a memory issue. Still have ~70GB on my SSD and have a 16GB RAM.

Deleted: profile.json 1.3 MB

profile.json 1.3 MB View Download

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

So looking at the profile, there are only a few things that stand out:


It looks to me like both a renderer's main thread and several of the main processes worker threads were blocked for ~26 seconds.  Only one of these threads (The a renderer's main thread) had a 26 second task - hannelAssociatedGroupController::AcceptOnProxyThread took 26 seconds.  I'm not sure what that does, or if that's a symptom instead of the culprit.  If you could restart Chrome, if you haven't already (To clear the old profiler data), and provide me more, that might be illuminating.

We also spend a lot of time trying to fetch the proxy script over DHCP.  This is unlikely the problem, as it shouldn't block any activity, but if you're not using a PAC script (If you don't know what this is, and are on a personal PC, you aren't), could you go to about:settings->advanced->open proxy settings->LAN settings->Disable "automatically detect settings"?

We spend a lot of time on DNS lookups, but those definitely aren't the problem, since they don't block anything.

Other than that, the log doesn't really contain anything that stands out.  A trace might be more helpful.

The fact that multiple threads across processes were all locked for 26 seconds makes me think this issue may well be that Chrome's being paged to disk (For unclear reasons), and it's taking a long time for it to become responsive again.

Alright so I've just switched on my pc from being off completely and it has happened again (so unfortunately no tracing information yet), I'll try to force it by putting the pc to sleep in a little while.

I explicitly checked the memory usage in task manager. There were 3 instances of a Google Chrome task, one being 30MB, the other two being 1-3MB. There were also 3 other tasks: Google Crash Handler, Google Crash Handler 32-Bit and a Google Installer (the other two I've seen but the installer is the first time I've seen it).

Please find attached another profiler dump, hopefully it's illuminating!
I'll also disable that setting and see what happens. If I go quiet for a couple of days it might mean that the issue is resolved but I'll be as active on here as possible sending all the profilers dumps (and hopefully traces) that I can when and if the problem re-occurs.

Deleted: profile.json 1013 KB

profile.json 1013 KB View Download

Just an update. Been using my pc today and Chrome hasn't been problematic once yet. I've turned it on, woken it up from sleep a couple of times; everything's working just fine!
Obviously it's still too early to say it's solved but it's looking good. Perhaps disabling that settings fixed it? For now I'll say yes, but time will tell. Windows needs to update yet again so that might break everything.

As per comment#11 issue seems is no longer reproducible. Hence marking this as Wont-fix.

@Reporter: Feel free to open a new issue if issue is seen again.

Thanks!