Thanks for the note about the security template; I'll work to have this updated.

Without more details (specifically, the URL on which you reproduced this problem, and/or a network log), the Chrome team will not be able to make progress on this report. 

If you can provide more details, including logs or other information about what your anti-virus program reported, we may be able to reactivate this issue and make progress.

For what it's worth, the most plausible scenario here is that a malicious site undertook an "annoyance" attack (e.g.  Issue 394296 ) which makes it the browser enter a tight loop. They then send an executable file download purporting to be the "fix" for the problem in the hopes that you will choose to run it (compromising your PC). Your AV program recognized the download as malware and blocked it, showing the warning you saw. By not running the executable, you remained protected.

It does not seem like   Issue 394296  - where no download happen. In this case the executable been run from browser without user prompt.

There is a Snippet  from history right before crash:
9:28 PM http://artemdragunov.livejournal.com/5025587.html#/comments
9:28 PM http://artemdragunov.livejournal.com/5025587.html#%2Fcomments
9:28 PM http://artemdragunov.livejournal.com/5025587.html#comments
9:27 PM http://artemdragunov.livejournal.com/

I am working with Cylance antivirus team to obtain the log. At the moment c:\windows\system32\werfault.exe is shown as blocked by CylancePROTECT antivirus.

Not sure will it be helpful, from Microsoft site: "Werfault.exe" is used for Windows Error Reporting. It is a feature that allows Microsoft to track and address errors relating to the operating system, Windows features, and applications. It gives you the option to send data about errors to Microsoft and to receive information about solutions."

In this case Werfault.exe was not downloaded but is a part of windows installation and meant to troubleshoot the frozen program. Most likely antivirus is not aware of such OS behavior.

The issue seems to be a duplicate of   Issue 394296 

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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