New issue
Advanced search Search tips
Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 838809
Owner: ----
Closed: May 2018
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Sign in to add a comment

Issue 839256: Random UI and content freeze on device using Intel Skylake HD Graphics (Windows 10)

Reported by, May 3 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36

Steps to reproduce the problem:
It's not clear the definite procedure to trigger the problem. On a Microsoft Surface Pro 4 (Skylake device), the following procedure will likely trigger the problem:
1. Open some tabs, play some videos or just open some random websites.
2. Open other applications. Chrome window is now inactive.
3. Perform tasks on other applications for a while. Go back to Chrome, the user interface might be unresponsive for a while (likely 30 seconds), then turned back to normal. If input method switch hotkey (Windows + Space) is pressed, the Window recovers immediately.

If Chrome has encountered the situation described above, it is likely to trigger another freeze soon, unless re-open Chrome.

The same issue also affects Visual Studio Code (which uses Chromium-based user interface engine).

What is the expected behavior?
The window should not randomly freeze.

What went wrong?
The window freeze. Cannot reproduce the problem on my other devices, which use Haswell-generation HD Graphics.

A trace file has been provided. The last few seconds have the problem occurred and recovered.

Did this work before? N/A 

Chrome version: 66.0.3359.139  Channel: stable
OS Version: 10.0
Flash Version: 

Not sure if related to IME, but the IME switching hotkey can mitigate the problem for a while. Then the problem will likely occur again.
19.0 MB Download

Comment 1 by, May 4 2018

Labels: Needs-Triage-M66

Comment 2 by, May 4 2018

Labels: Triaged-ET
Mergedinto: 838809
Status: Duplicate (was: Unconfirmed)
noc@ Thanks for the issue.

This issue seems to similar to  issue 838809 . Hence merging this issue to  issue 838809 .
Please feel free to undupe if this is not the case.


Sign in to add a comment