Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Google Chrome Causing Freezing and Crashing on New Mac Notebooks
- Thread starter MacRumors
- Start date
- Sort by reaction score
It is actually a relief to see this. I've had three lock-ups on my new Air. It's nice to know that it's not just me.
Hopefully it'll all be fixed soon.
Hopefully it'll all be fixed soon.
I'm actually having these issues on my new MB Air. Last night I actually got the "Hold the power button for restart" message.
However, Chrome has not yet prompted me to update for the temporary fix. Anyone know what gives?
However, Chrome has not yet prompted me to update for the temporary fix. Anyone know what gives?
Not really sure what your point is, typing in this text box created a post on macrumors.
My point is that most interaction with the browser doesn't involve typing into the URL bar. I clicked on a bookmark, a couple links, typed a post, and didn't touch the URL bar once.
An advantage can also be a comparative claim in the context in which it is used. In this case, the advantages I've listed are factors compared with "your average browser".
It's great to hear that Safari 6 is becoming more like Google Chrome. Safari is definitely improving, but at the time when I started using Chrome Safari was slower, had a clunkier interface, didn't like how the text-prediction worked in the adress bar, didn't use separate processes for each tab (still probably isn't using them), didn't have extensions (has them since 2010) etc. etc.
That's because Chrome doesn't pass your browsing habits. This is no different than using "Google Instant" in their search page. They've simply integrated it to their omnibar.
And guess what, coming soon to a Safari near you :
http://www.macworld.com/article/1165466/mountain_lion_hands_on_with_safari.html
So I'm guessing users who want to hide their deep dark secrets they type into omnibars won't be upgrading to Mountain Lion, right ? rrrrriiiight ?
Again, Google mostly collects your browsing habits through Google Analytics. That's how they feed their ad targetting datasets. Google Analytics is set up by webmasters who use Google as an ad service. If you run a NoScript extension, you'll see about every page on the Internet has a <script> tag trying to execute some script off of analytics.google.com. Internet Explorer, Safari, Firefox, Chrome, Opera, any browser just executes this, takes your "browsing habits" and sends them to Google.
Chrome is no different. The Omnibar is not evil. In fact, it's convenient. Firefox has the same "Google Instant" integration in their search bar. It does the same thing.
Pretty funny though that this thread is about a GPU driver bug in OS X that causes a Kernel Panic from userspace, yet people are oh so concerned about their privacy over using a public network. Talk about not seeing the forest for the trees. That bug could potentially be turned into a DoS or privilege escalation depending on the conditions that trigger. Being able to crash the kernel from userspace is not a good sign, this is a pretty serious bug in the Intel driver.
Sure, depending on user habits and so on. But it should give a rough equivalence to the browsing history, at least in my case I find it much faster to type the first few letters in the url and let autocomplete do it's job. But you have a point.
Cant believe all the people complaining about Chrome here and in the thread about it coming to iOS there is nothing but good. Ive been using Chrome for over 2 years now on my Mac with absolutely no problems...I have even moved to the Canary channel for a while because it was the one that had the gesture. (The Canary channel is the first channel that new features show up on, once stable they get pushed to the public-stable version)
You'd think people who don't like or use Chrome would feel unconcerned and would just move on. It's curious how people take up arms and actively crusade against it. What's with the agenda ? Mystifying to say the least.
I agree that they need to make OS X more stable. I hope the sandboxing practices help.
Just yesterday I started playing a movie in VLC on my MBP and its interface became unresponsive. When I tried to Force Quit VLC, it wouldn't do anything - the video kept playing. At that point I tried shutting down OS X and it couldn't do that, so I had to resort to a hard reset.
I remember when Windows was like this, around the time of 98/XP when a single app could bring down the entire system. They've really made it much more robust since 7/8, so Apple should too. OS X rarely has problems for me, but when it does, they are embarrassingly serious.
Just yesterday I started playing a movie in VLC on my MBP and its interface became unresponsive. When I tried to Force Quit VLC, it wouldn't do anything - the video kept playing. At that point I tried shutting down OS X and it couldn't do that, so I had to resort to a hard reset.
I remember when Windows was like this, around the time of 98/XP when a single app could bring down the entire system. They've really made it much more robust since 7/8, so Apple should too. OS X rarely has problems for me, but when it does, they are embarrassingly serious.
Sandboxing doesn't help with these types of bug. Chrome would have asked and been granted a GPU usage entitlement and would have a valid GL rendering context and would still trigger the bug through the sandbox
I'm going to say that Chrome is a better browser than Safari. Way more speedy and light to use. And every time I use YouTube Safari can't handle the playback on my 2011 MBP.
That explains why Chrome would drain the RAM on my MBP (older model) after just opening a few pages, and not give it back after closing.
And that's besides making my MBP run slower.
In Safari's case, I found the problem to be with Javascript. Website with lots of Javascript would drain the RAM on my MBP fairly quickly. Disabling Javascript makes a huge difference, but we still need to use it.
And that's besides making my MBP run slower.
In Safari's case, I found the problem to be with Javascript. Website with lots of Javascript would drain the RAM on my MBP fairly quickly. Disabling Javascript makes a huge difference, but we still need to use it.
Something people just don't realise and that is never picked up on by the press is how potentially insecure drivers are.
Graphics drivers in particular are written with performance in mind - they don't have time to check whether the programmer is trying to crash the computer.
I don't imagine that Google has rushed out any new graphics code for the Intel HD 4000 series on Mac OS X, so it's more likely that something they've been using on other GPUs in Mac OS X doesn't work with the current driver.
Apple's approach to GPU updates is really quite poor, especially for Intel GPUs.
Graphics drivers in particular are written with performance in mind - they don't have time to check whether the programmer is trying to crash the computer.
I don't imagine that Google has rushed out any new graphics code for the Intel HD 4000 series on Mac OS X, so it's more likely that something they've been using on other GPUs in Mac OS X doesn't work with the current driver.
Apple's approach to GPU updates is really quite poor, especially for Intel GPUs.
Just MacBook Airs?
My google chrome browser as of yesterday stopped loading any page. It loads the window but I always get their ohsoclever "Aw, snap" broken page for every attempt to load a page now on my Windows 7 machine.
It's been failing consistently as Firefox has recently. Time to move on, probably to safari on Windows.
My google chrome browser as of yesterday stopped loading any page. It loads the window but I always get their ohsoclever "Aw, snap" broken page for every attempt to load a page now on my Windows 7 machine.
It's been failing consistently as Firefox has recently. Time to move on, probably to safari on Windows.
They're doing away with Flash; Chrome are you next?/sarcasm
I've actually preferred this over FireFox, though I do like the Safari as its improved havent had any issues with our other machines yet
I've actually preferred this over FireFox, though I do like the Safari as its improved havent had any issues with our other machines yet
Interesting. I have had similar problems with Chrome on my 15" MacBook Pro. The graphics of Chrome cause the computer to switch between the Intel and AMD graphics repeatedly and lead to kernel panics. I uninstalled Chrome and have been using Safari without problem.
BTW, the use of two graphics cars is one of the stupidest decisions. You can always tell when the computer switches because the fans really kick in and the thing gets very hot.
BTW, the use of two graphics cars is one of the stupidest decisions. You can always tell when the computer switches because the fans really kick in and the thing gets very hot.
Yeah, it's so very stupid to offer extended battery life when you don't need GPU power, and very good performance when you do. All because a "fan kicks in". *sigh*.
GG.
And that's why, you don't use Google software.
Bugs will always occur in software. It's just that this bug exposed an even bigger critical bug within Mac OS X.
As it's only happing with the HD4000, it's likely to be an issue within some graphics driver code that Intel has supplied Apple for incorporation within Mac OS X.