Chrome says "Processing Request..." at Launch for every website
Reported by
abdulham...@gmail.com,
Oct 6 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Example URL: https://www.facebook.com/ Steps to reproduce the problem: 1. Turn on PC 2. Launch Chrome 3. Try to load any page What is the expected behavior? Not to wait so long. At this rate I will be changing to Mozilla or something. What went wrong? Whenever I launch Chrome (Version 61.0.3163.100) and try to load any webpage in any tab it hangs on "Processing Request..." for a very long time until I am forced to close Chrome and end task on any Chrome service in the task manager. I have to wait ages to just get it to work and hop on a webpage, such as Facebook. Does it occur on multiple sites: Yes Is it a problem with a plugin? N/A Did this work before? N/A Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 27.0 r0 I have uBlock Origin and Adblock Plus blocking ads at all times. I also have Tampermonkey downloaded (only runs scripts for 1 or 2 websites) and I have Google Docs, Google Docs Offline and Google Sheets enabled, as well as Google Slides (disabled).
,
Oct 6 2017
That's what the network stack returns when it's waiting for the embedder (The rest of Chrome) to do something. That can include extensions, though we should generally blame one of the extensions we're waiting on when that's the case. I'd suggest you try to disable extensions, and see if that fixes the problem.
,
Oct 6 2017
,
Oct 7 2017
I reset Chrome and disabled all extensions besides the Google ones and uBlock and ABP. I think it may have been Tampermonkey stalling Chrome. Hopefully they fix it. Thanks to all that answered!
,
Oct 7 2017
Thank you for providing more feedback. Adding requester "bnc@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
,
Oct 9 2017
@abdulhamze17 -- Based on your Comment #4, can we close this issue. Thanks!
,
Oct 9 2017
Thank you for getting back. As this issue is likely not caused by Chrome itself, I'm closing it.
,
Oct 11 2017
I was wrong. IT IS GOOGLE CHROME. Fixed for like 1 day and then it goes back to its old, slow and crashing self. I have gone with Firefox now, 10 times better. Honestly, Chrome is so bad. Perhaps in the future I'll come back if Google proves they can make a working browser that doesn't waste so much time and use so much resources. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by schenney@chromium.org
, Oct 6 2017