Tested the issue on latest stable #59.0.3071.115 on Win 10 and was unable to reproduce the issue as per the steps mentioned in original comment.

@jamilbn: Could you please provide us a crash server I'd by navigating to chrome://crashes for further triaging of the issue.

Thanks!!

Just enabled the Crash reporting.

How do I provide a crash server?

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

Enabled the crash reporting on settings and put the computer do sleep.

Waited a few minutes and waked it from sleep again and opened Chrome.
Sometimes the browser dont freeze before I try to load a website, sometimes
it freezes when I open a website.

Opened the web.whatsapp.com that was open on my desktop and everything
froze like always.
Rebooted the computer without trying to kill the chrome process and no
crash was detected.

The curious thing is that the whatsapp that was open on the desktop didn't
close. Usually when you try to open a whatsapp on another tab or machine
the previous one closes.

Browser frozen again.

Never waited with it frozen. Left the machine there with the Browser
showing not responding.
It seens that only the GUI is frozen.

After a few long minutes the site I started to load worked and when I tried
to click the GUI frozen again.

Deleted: Capture.PNG 24.1 KB

	Capture.PNG 24.1 KB View Download

Tried to kill Google Chrome. Every other process ended except the 10500 that is not responding and can't be killed. the taskkill /F /T /PID 10500 says the process could not be terminated. Reason: There is no running instance of the task. But the task is there. 

After a couple minues the 10500 disappears and them I can load chrome again.
Still Crashes (0) showing when I access chrome://crashes

OS full freeze ever since Chrome .115 (multiple Win8.1 PC's).
No crash report, only waiting (sometimes) or hardware reset button. Productivity on multiple workstations (different location, not related to each other) took a full nose dive (because these freezes take at least 20 minutes of my time). Only way to solve until now is to use Firefox.

Signs browser is affected (because I have _some_ systems that are not affected). And also signs it's in the underlying Chromium code, not just Chrome, since Opera has EXACTLY the same problems with the latest update:

- The menu button isn't reacting
- in web.whatsapp.com or web.telegram.org, the conversation list to the left can be clicked, but there's no reaction on the right (conversation should appear).
- in gmail, after a few clicks and browsing, the More button (on top, when a message is selected), doesn't activate anymore.

Sadly, no common factor on those affected and non-affected PC's can be found, other than Chrome/Opera freezing it.
When those 3 problems are encountered,  you can be sure it will freeze after a while (unpredictable how long, but the more you browse, the faster it will happen). You can also be sure, a full uninstall (including Appdata/Localappdata/Roaming folders) and reboot, and re-install of the browser doesn't work (the signs can be tested directly after install, and you'll see it's consistently not working).

Hope the bug can be found in the original Chromium code.

Just found a pen input thread: 

https://bugs.chromium.org/p/chromium/issues/detail?id=732158

Seems that's more where my bug lies. Are you having pen input also by any chance?

The device I'm having this issue does have pen and touch input. But it's freezing from using the touchpad. Most of the times when I open the lid from sleep. After a few seconds the browser freezes.

But sometimes it happens during usage. Will watch if it's when I use touch. The touch feature of Windows 10 is just great i use a mix of touch and touchpad.

At first I thought it was some kind of rootkit because you just can't kill the chrome process. After issuing a kill -force the process keeps running for about 2 or 3 minutes.

Havin pen input is just another hint for the Chromium team to solve then! It's still the only common thread I've seen for the later versions of Chrome. Maybe just having the pen input there, even not used actively, is enough to freeze the whole OS.
For your workaround for now, is to fully uninstall Pen input (disconnect it is enough if you never installed drivers).
For me, I need my pen, I'll just have to make do with Firefox till it's solved

But why this started with Creator Update? I didn't had this issue before
this last Windows 10 Major update. Perhaps they changed something in the
Pen Input system of the SO?

I don't think it's fully a Creator Update error, as pen input on Win8.1 causes freezing issues as well (I have 2 Win8.1 with this problem, also having pen input). It could also be another Chrome update that coincided with the same time as Creator Update.
Seeing the other threads, they're closing in on solving it.

This is dupe of  issue#724836  which is already fixed on latest Chrome Beta(60.0.3112.66), Can someone please try the Beta and let us know if you still able to reproduce the issue.

@ jamilbn : As per comment #14 could you Please create new profile without extensions and apps.Re-check once in latest Stable/Beta #60.0.3112.78 and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance.

After I installed it I couldn't recreate the freeze process. It almost always happened after I wake the machine from sleep. Some rare ocasions during normal use. Everything was fine until I woke it from sleep today and it just frozen like before. So no, chrome 60 didn't solved this issue. Maybe mine is not related to the pen and ink input.

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

While freezing has been solved, sadly, pen/graphic tablet users are now at an disadvantage (most interactive sites like web.whatsapp.com, web.telegram.org, but really almost ALL websites will have quirks now), as many clicks are not registered anymore. The usage (full pen control, NO FREEZING) from 2 months ago seems like a distant dream now, as it seems "disabling pen support" was the solution, instead of really fixing the bug.

Here I'm still getting a lot of freezing. The GUI freezes but the browser keeps working. I tested this by opening a few sites. When I click the address bar and type something it works and open the site. But the GUI is frozen so nothing visual happnes. As I said before, this started with the creators update.

We have multiple users reporting frozen browsers since version 59 - all on Windows.  Problem is intermittent, but very wide spread.  GUI will go unresponsive and, after 20-30 seconds, respond again or ask to Wait/Kill tabs.

Much more than 30 seconds here. The bad part is that I can't kill it. First I thouht it was some kind of malware. The process is frozen and even kill force can't get rid of it. After a while it get's killed. More than a minute. The only way to launch the browser again without freezin is to reboot.

The freezes started to become more and more frequently. Now I'm having to reboot 2 or 3 times to get the browser working.

@Reporter: Could you please check the issue on latest stable #61.0.3163.100 or on latest canary 63.0.3236.0 and update the behavior.

Thanks!

I'm using  61.0.3163.100 and can't reproduce the error for a while now. You can close this.

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

Marking this issue as WontFix as per the C #25.

jamilbn@ Could you please file a new bug if the issue still exists in latest chrome builds.

Thanks!