Comments on: Fix: Page Unresponsive ‘Kill Pages’ error in Google Chrome browser

By: ToeKneeOh

ToeKneeOh — Fri, 08 Apr 2022 00:55:34 +0000

Is anyone else experiencing rapidly rising rates of Unresponsive Chrome pages over the last 2 weeks, and could that be due to the new Chrome 100 update? And if it is the reason, are there any recommended hints for solutions or work-arounds?
Thanks –

By: Kushal Azza

Kushal Azza — Tue, 22 Mar 2022 11:28:07 +0000

In reply to D. The Chrome browser is heavy on the system resources and if we use the extensions, then totally burnout the machine. Perhaps the 1300MHz is not able to give the required juice to render even the lightest of light pages. Even I have an old Dell PC running with Core i3 at 1700MHz, the results were the same as yours until I upgraded from HDD to SSD. It's better now but still stuck at times.

By: D

Tue, 22 Mar 2022 09:06:03 +0000

None of the above fixes explain why Chrome on a five year old quadcore at 1300 MHz goes to ‘page unresponsive’ when asked to load a minimal test webpage of < 0.2 MB. Even the banner image in it is highly compressed to take less than a tenth of a second to go through a 10Mb/s old download connection, yet a minute later the browser is still hanging around with 'page unresponsive'.

I suspect that the request from the browser to the DNS (domain name server) got 'lost in the post' because mousing to the right end of the typed webpage address bar in the browser window and hitting enter gets instant page load.

One might expect that a 'suspected lost DNS query' detected as 'page unresponsive' should be built into the browser to try resending the web page request once before annoying the user with a stupid timewaster notice.