• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Chrome takes ages to open google.

Red Squirrel

No Lifer
This is a weird one. In FF I was used to always hitting the home button to get a Google search page, in chrome there's no home button so I just added a bookmark button with Google. Whenever I press it, it takes a good 10 seconds for Google to load, and only does this to Google. Anyone ever have this issue? I find it kind of ironic considering Chrome is made by Google. 😱
 
I've gotten really used to typing goo<tab> then entering search terms directly into the URL bar, but I just tested and Google came up in ~1s here in Chrome on Linux.
 
Google search is built into the address bar. Just type in your query and press enter. Also, there is a home button in Chrome, you can activate or deactivate it in settings and set google.com as your home. But googling through the address bar is the fastest way 🙂
 
5.0.317.2 dev I was just browsing about 6 or 7 tabs open in 1 window and noticed in taskmgr that my ram usage was at 1.7gb, I closed Chrome it dropped by 800mb to 920mb.

Chrome was using 800mb.... Jezuz
 
It's using "only" 45MB for me right now, but I noticed the same with firefox, it would start low and go high.

Why can't anyone write an app that does not leak like a pregnant woman?

I'm trying to just get used to typing my search directly in the address bar, but I'm so used to just going straight to Google. Still takes a good 10-20 secs before it loads when I go there with chrome though, kinda weird. At work it seems fine.
 
I'm inclined to believe most memory leaks are caused by plugins such as flash and java. If the websites were exclusively html, there probably wouldn't be any problems at all.
 
I don't have to be a mechanic to complain about cars, do I?

And I just use the address bar method. Seems to work great.

No, but it's a lot more credible if you actually know what you're talking about. And RS has this tendency to think he can write a better version of whatever he's complaining about.
 
High memory usage and "leaks" are not the same thing. Users expect web pages to load as quickly as possible these days, and to achieve that all major browsers need to remove IO bottlenecks and cache things in memory. That's the tradeoff, performance for footprint.

Extensions and plugins complicate the issue 100-fold.
 
Back
Top