New issue
Advanced search Search tips

Issue 702960 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome periodically freezes on Fedora 25

Reported by leoscha...@gmail.com, Mar 19 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36

Steps to reproduce the problem:
1. Open Chrome
2. Normal usage (3-5 open tabs)

What is the expected behavior?

What went wrong?
Chrome freezes (few seconds up to multiple minutes, sometimes didn't recover at all). Sometimes freezes the entire desktop environment, but in most cases, all other applications continue responding.

Did this work before? N/A 

Chrome version: 57.0.2987.110  Channel: stable
OS Version: Fedora 25
Flash Version: 

Fedora 25 stock kernel, 4.9.14 (see https://apps.fedoraproject.org/packages/kernel). 

Skylake thinkpad, i5-6200U with integrated graphics and high DPI screen. Chrome respects the system DPI and scales up accordingly. No compositor running.

Troubleshooting steps that did not resolve the issue:

  * Disabling GPU rasterization, but leaving GPU rendering enabled
  * --force-device-scale-factor=1
  * Upgrading kernel to rawhide (4.11-rc2)

Issue is perfectly reproducible on my machine. No messages in the debug log when it happens, no CPU spike, just hangs.

Issue does not occur for me when either

  * The GPU process is disabled (still hangs for <1s from time to time, but that might very well be unrelated but I wouldn't rule it out)
  * The internal screen is disabled and two external monitors are used instead (both with xrandr --scale 1.5x1.5, may or may not be relevant), even with GPU rendering and rasterization enabled.

Related discussions:

  * https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/DDAH2WXCZYIDGWWB7PWW3TW2WO6MGPBD/
  * https://ask.fedoraproject.org/en/question/98621/google-chrome-freezes-and-other-amdati-issue/
  * https://ask.fedoraproject.org/en/question/98908/fedora-25-chrome-freezes-gpu-related-problem/
  * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848895 (not 100% sure if same issue)
 
related to:
https://bugs.chromium.org/p/chromium/issues/detail?id=702968

I suscpect it's because of low VRam. I have only 2Gb on my NVidia card.
Cc: rbasuvula@chromium.org
Labels: Needs-Feedback
Tested in chrome # 57.0.2987.110 and Canary #59.0.3046.0 on Fedora 23 & 24 and not able to reproduce the issue.Please find the screen cast for your reference.

@ leoschabel: Could you please let me know if i have missed anything and if possible, please create new profile without extensions and apps.Re-check once and let us know the observation of the issue which would help us to triage the issue further.

Thanks in Advance.
702960.ogv
21.7 MB Download
Thank you!

I tried it with a clean Fedora 25 install, wasn't able to reproduce it and narrowed it down to the following set of custom, non-default kernel options that I had set:

i915.enable_psr=1
i915.semaphores=1
i915.enable_fbc=1
nohz_full=1

Removing those solved the issue, but increased baseline power usage by ~2W. 

Since those are commonly recommended for power saving (and maybe even set by power management scripts), it might explain why other users are affected.

I'm a bit short on time right now so I wasn't able to investigate further, I'll check which of these four is the culprit as soon as possible. I used those same options all the way back to F23 so it's probably a recent regression.
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 20 2017

Labels: -Needs-Feedback
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
Labels: Needs-Triage-M57
@ leoschabel : Could you please update on comment #3.

Thank you!
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback
Friendly ping!!
@ leoschabel ,
Could you please update the thread with latest observations.
Thank you!
you can close it, since Chrome updated, it's no more happening 
Status: WontFix (was: Unconfirmed)
Closing as per c#8, and because reporter is not responding

Sign in to add a comment