Google Chrome is Freezing Intermittently With the Windows 10 April 2018 Update, Users Say (neowin.net)
Several users who have updated their computers to Windows 10 April 2018 Update are reporting that Chrome is freezing their machines. From a report: I have now used the April 2018 Update for nearly 24 hours and the same problem has presented itself no less than five times. For a machine - which was working perfectly prior to the update - with a Core i7 CPU, 16GB of RAM, and a 512GB SSD, I naturally resorted to Reddit and Microsoft forum threads to see if others were experiencing the issue. It appears that several users on Reddit (spotted by Softpedia) with machines sporting varying configurations are experiencing the problem as well, and the only fix to it is the one I found too; that is, putting the laptop to sleep using the power button or closing the lid.
I switched away from Firefox recently for various reasons and Chrome has been a sore disappointment. Tabs crash constantly, GIFS stop working (shows first frame then goes black), the addon ecosystem is worse than Firefox - there's more of them, just poorly made and option poor.
There's not a single browser on the market today that I would actively recommend. Just an array of mediocrity.
.... that the problem has something to do with hardware acceleration, the endless fountain of browser glitches.
"Prediction: within 10 years, Windows will be a Linux distribution." Me, 7-6-2016
This would be the first time a microsoft update has caused problems for a rival's products or programs.
Because this would be the first ever recorded such instances I deem it to be highly unlikely.
...so nothing to see here.
This is why enterprises and power users are staying with LTSB, Windows 7 and even XP. We don't want sudden updates breaking our stuff. Microsoft needs to learn to slow down and do proper tetsing instead of this Windows as a service fad.
And I checked the resource usage, one tab was using 2 gigs of RAM for some reason! ACK!
So you're saying you’re not seeing anything out of the ordinary?
#DeleteChrome
I install the new update yesterday, make the mandatory 5 reboots. This morning, the window's login screen was freezing for a good 5 minutes...
Then when I finally get there, windows ask me to change my login credential... and freeze... then updating language module and freeze.. adding I don't know how many new keyboard in the keyboard bar....
When, we compare this to mature OS like Ubuntu or Mint... Windows take like 3 hours to update on my i5 12g ram 10krpm computer after the download... without counting the reboots... Ubuntu ou Mint can date like 15 minutes on the same hardware..
Windows is not ready for business ... ;-)
Ceci n'est pas une Signature !
People let their browser open longer and longer on the same page, opening more pages...
And many web sites (Facebook to begin with) allocate objects, create circular references and don't break the reference cycle because "dropping" the object, leading to a cycle of objects (elements, functions and closures) which can't be freed by the garbage collect.
Don't blame the browser, blame the web sites creator who don't care about cleaning their junk.
Wait, sounds familiar somehow...
Yes, flamebait subject. But hear me out... given the growing interest in data privacy and concern about the mining of our online activities, Chrome's horrendous tendency to take over all your computers' RAM and CPU, the latest Firefox being measurably faster than Chrome, aggressive and intrusive bundling of trojan Chrome installs into unrelated apps, and now Chrome pulling an IE in pushing proprietary markup that encourages the making of websites that ONLY work in Chrome, why are people still giving Google a pass and using an inferior/arrogant browser when there is a better option?
Full disclosure, I'm not the biggest Chrome fan, and not the biggest Google fan, either. However, I don't generally get caught up in browser wars; I don't generally tell Chrome users to use other browsers if they're happy with it and their sites load.
However, about a month ago, Chrome started acting really weird. Sites would time out, or take over a minute to load, on well-spec'd computers with no malware and wired network connections. After trying every tweak I could think of, I tried those same sites in Firefox and they loaded in the 2-3 seconds they were supposed to. Over the past month, that experience has repeated itself across users with nothing in common except Chrome, and "switching to Firefox" completely resolving their issues.
I'm sure the April update sucks; I'm hard pressed to point to a Win10 feature update that provided a useful feature that justified the update installation time. However, I'm hard pressed to not give Google at least some share of the blame when a number of users (some of which still using Windows 7) had issues with Chrome that were solved by switching to Firefox.
Sounds like Microsoft and Google's telemetry collided and is causing chaos everywhere. The two threads are arguing about who gets to take what.
Fake news! No crashes. Works perfe
Table-ized A.I.
Let me guess... the Edge browser is running faster than ever..?
It ain't done 'til Lotus won't run...
-Myke
I am pretty satisfied with Opera on Android. It is the only browser on Android that I know of that you can force zoom to be enabled and it rewraps the resized text to be justified to your screen size. That is a very powerful feature.
RAM is a expense, expenses must be controlled. The more a web browser takes up, the less of the same resource is available for other tasks.
Whe you only have to budget for one PC with 16GB of RAM, it may not seem like a lot. When you have to budget for hundreds or even thousands of PCs, against a Walmart razor thin margin ecosystem, 16GB is an incredible expense. And one can't raise margins to cover the cost of a better rig, because the lowest bidder wins. This trickles down to the employee who can't afford more than $400 per cycle for a PC, and whose 4GB/dual core box isn't past the 8 year cycle yet.
Excessive memory usage by websites and browsers, and excessive bandwidth usage by websites is both greed and gluttony, and is disrespectful to the working class. Its like a pot of gold at the end of the rainbow, except in this case that pot of gold is affordable computing. By the time we get 10mbps 4G LTE across the country, the web is going to require 100mbps minimum. Afford 16 GB of RAM, and the minimum is now 64GB.
Allowing the stability of YOUR system to be dependent on remote hosts coding correctly is folly. Even if most sites comply, some won't. A fraction of those may even be malicious. Browsers need to be able to detect when something is going off the rails and kill a thread -- or at least suspend it and ask the user -- because expecting not to encounter intentional abuse is tantamount to wearing a big "pwn me" sign.
How is the Riemann zeta function like Trump rallies? Both have an endless number of trivial zeros.
Possible, perhaps. Efficient and bug free on initial push/deployment? Unlikely. Such features would more likely cause the features you are describing by the browser trying to manage all that with little telemetry or other feedback data on what the errors or issues actually are. Also not really worth spending time writing a LOT of code to fix a problem only one or two people have. Wouldn't surprise me if those changes reach $1,000,000 in development costs before it was all said and done.
As for suggestions:
You say bandwidth is not an issue, nor does the significantly above average RAM quantity appear to be insufficient, so,...
120 tabs open and bandwidth isn't a factor???
1. Get an SSD. Make sure there is no bottleneck for simultaneous reads and writes to randomly accessed cache data.
2. Try disabling other services and other apps to reduce the difficulty of managing multiple threads.
3. Ideally, as a rule of thumb one shouldn't let the number of tabs exceed 1.5 times the number of cores on the machine, to avoid contention of resources. Especially when a heavy resource page like a video stream is being displayed. Heavy resource pages, such as multimedia streams, will likely need two or three cores exclusively to avoid contention of resources for an uninterrupted stream.
4. Update your graphics card drivers.
5. Get a dedicated graphics card for proper hardware accelleration. Intel should be able to handle a single 1080p video fine. 120 tabs of hardware accellerated content alongside even a single 1080p stream will likely require a more powerful GPU.
6. Make sure you're hardwired in using gigabit ethernet. Wifi introduces a bunch of issues into the bandwidth stream, especially when the connection/channel is shared by multiple devices.