Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Everything is fine for me in Canada.

Though I have seen this bug crop up now and then, where safari on my iPad would crash when trying to enter an url.
[doublepost=1453907189][/doublepost]
I agree this is NOT a fix... But what has it got to do with Google??
The suggestions are probably populated by the google search engine backend.
 
I wonder if this is actually a problem with Google search autocomplete because I'm not experiencing the problem and I use duckduckgo which has its own autocomplete. Obviously still a bug in Safari but perhaps triggered by Google.

Yup, I have not experienced any issues with Safari on Mac. I use DuckDuckGo, as well. And Yahoo! on my iPhone. I do use Google, but only by manually navigating to the site, not as part of my default settings.
[doublepost=1453907949][/doublepost]I'm not sure if it's related, but ever since 10.11.3, my Mac has consumed tons of disk space randomly, to the point where I had to offline my entire Dropbox folder to an SD Card just to keep my computer from running out of disk space.
 
Thanks for the tip.... it's working properly again.. Q? Will I need to turn it back on at some point?? (tick safari suggestions again) in the future?
 
Not just a service issue, also a bug. Just because a service goes down, it should not cause an app to crash. Did nobody at Apple test such a scenario before releasing the browser? I guess not.
 
I've seen reports of other from other forums disabling the suggestions doesn't work. but it could just be a cache issue *shrugs*
 
I wonder if this is actually a problem with Google search autocomplete because I'm not experiencing the problem and I use duckduckgo which has its own autocomplete. Obviously still a bug in Safari but perhaps triggered by Google.
It's not the search engine … I had duckduckgo set as default and Safari crashed until I turned off Safari suggestions.
 
safari 9.0.3 (11601.4.4) and os x 10.11.3 (15D21). No problems. Am I missing anything?
 
I wonder if this is actually a problem with Google search autocomplete because I'm not experiencing the problem and I use duckduckgo which has its own autocomplete. Obviously still a bug in Safari but perhaps triggered by Google.

Why does this crap ever get upvoted? It's Apple - once again - who ****ed us deep from behind! A wrongly configured web service... nah okay. But a client crashing due to bogus (or no) data? **** me hard! That's retarded, Apple!
 
Is this related at all to the safaricrash-dot-com prank site that does the same thing? I read about that spreading this morning...
 
How did this bypass their QA department?

What QA department?
[doublepost=1453909671][/doublepost]
Is this related at all to the safaricrash-dot-com prank site that does the same thing? I read about that spreading this morning...

No, it's related to the Apple-****ed-up-hard-again issue that popped up again.
[doublepost=1453909766][/doublepost]
Yup, I have not experienced any issues with Safari on Mac. I use DuckDuckGo, as well. And Yahoo! on my iPhone. I do use Google, but only by manually navigating to the site, not as part of my default settings.
[doublepost=1453907949][/doublepost]I'm not sure if it's related, but ever since 10.11.3, my Mac has consumed tons of disk space randomly, to the point where I had to offline my entire Dropbox folder to an SD Card just to keep my computer from running out of disk space.

It has nothing to do with the Search Engine's Suggestions! Be it Google, DuckDuckGo or whatever! It's Safari Suggestions that's the culprit! All Apple's fault!

And a client that trips over a bogus web service? Go figure!
 
I was just having all sorts of weird problems on my Mac when I saw this. The workaround worked for me, so thanks MacRumors!
 
Why does this crap ever get upvoted? It's Apple - once again - who ****ed us deep from behind! A wrongly configured web service... nah okay. But a client crashing due to bogus (or no) data? **** me hard! That's retarded, Apple!

Apple's fault? Yes. Stupid mistake? Yes.

Does it qualify as a deep a** f***ing? Not really. No harm done besides a minor inconvenience. No data leaks, no data loss, no bricked hardware, no diving into the Terminal to temporarily fix.

It's another embarrassing blunder for Apple, but they've had much worse mishaps by comparison. Breathe.
 
No problems here in S. AZ. Safari Version 9.0.3 (11601.4.4) and that is no problems on my macs (3) or idevices (3).
 
This isn't a FIX, it is a WORK-AROUND until Apple/Google provide the real FIX.

I believe the correct terminology is "kludge". :)

Really tired of people throwing this comment out when something Apple goes awry. You obviously have never used Windows, either standalone or in a network environment for any length of time. If you have, you would understand Apples phrase "it just works" more clearly and know that it's correct 99% of the time. Windows on the other hand, good luck.

I've used Windows just about every day for the last 20 years, even though I'd switched my personal computing back to Mac a little over 7 years ago. With each update, I perceive the gap between the two environments closing; I don't attribute it to a substantial improvement in Windows, either. Goofy things in the same ballpark as this issue have always been staples of the Windows environment and up until 4-5 years ago were virtually non-existent on Macs. Contrast to today.

Apparently being better excuses you from continuous improvement? Sounds like a good plan for no longer being better. Excusing one's own faults by blaming another is the game of politicians and let's not let that disease spread elsewhere.

You'll also note that Apple conspicuously no longer uses the subject phrase. They don't need to. Most Apple buyers don't shop for quality because they either expect it to be baked in or are just following the crowd. If Apple says it's quality, then it must be so - until it isn't.
 
Last edited:
  • Like
Reactions: Martyimac
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.