"page unresponsive" dialog popsup |
||||||
Issue descriptionGoogle Chrome 71.0.3578.80 (Official Build) (64-bit) Revision 2ac50e7249fbd55e6f517a28131605c9fb9fe897-refs/branch-heads/3578@{#860} OS Linux What steps will reproduce the problem? (1) goto drive.google.com What is the expected result? page finish loading and no error What happens instead? page never finish loading and pop up dialog https://screenshot.googleplex.com/qGQr9moT0E6.png Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Dec 5
dev console points to https://www.chromestatus.com/feature/5527160148197376
,
Dec 5
after disable "Enable resource load throttling" in chrome://flags drive.google.com loads without problem.
,
Dec 5
,
Dec 6
Are you really sure if that flag consistently affects the reproduction? That resource load throttling never affect the foreground page. Also even background pages, when you see that console messages, every suspended requests are already resumed. It also should not result in 'Page Unresponsive' popup. Possible root is slow loading reveals hidden JavaScript issues in the page. Add Blink>Scheduling just in case. Also, I will CC the reporter to 897270, that may be related (but should already be fixed in m71?)
,
Dec 6
Can you reproduce this with a new profile with no Chrome Extensions? Also how often does this happen? If you only see this issue on a specific profile, recording a trace (https://www.chromium.org/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs) would help investigation.
,
Dec 6
,
Dec 6
It was repro on every reload of drive.google.com yesterday. I turn resource load throttling to enable just now, and no longer repro. It was happening not on drive but a few other pages yesterday. On a separate note, the flag should be just called 'resource load throttling' (without the Enable), the enable and disable should be done with the flag not part of the flag name, its confusing to read otherwise.
,
Dec 7
Please check Variations list in chrome://version when you see the problem again. Also, if it can be repro on every reload once if happen, please try recording a trace, and capturing network log at chrome://net-export/ Also note that Chrome Extensions have power to cause this kind of problems. So please make sure if the problem can happen with no Extension.
,
Dec 9
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by dchan@google.com
, Dec 5