Skip to main content
  1. Home
  2. Phones
  3. Apple
  4. Computing
  5. Mobile
  6. News

Apple fixes the bug causing Safari to crash on Mac and iOS devices

Add as a preferred source on Google

This hasn’t been a great week for users of Apple’s Safari browser. First there was a link to a prank website that crashes the browser being passed around, and more recently the browser began crashing for a different, entirely unrelated reason.

Some users were finding that Safari crashed every time they tried to enter a search, no matter whether they’re using it on a Mac, iPhone, or iPad. A Reddit thread posted this morning has already grown to more than 150 comments, with users noting the crash was happening across different hardware and OS versions.

Recommended Videos

Updated on 01/27/2016 by Julian Chokkattu: Added news of Apple offering a fix for the Safari issue. 

Apple now seems to have fixed the Safari crash bug that affected many users, and according to BBC Newsthe problem may have arisen from Apple’s data centers, instead of the Safari app itself. The fix may take some time to reach all affected iOS users. But if you’re still waiting for the fix, you can go to your Safari settings and hit “Clear history and website data,” and the browser should go back to working like normal.

The bug appeared to be related to Safari Suggestions. When users start to enter text, it is sent to Apple servers in order to retrieve information to autocomplete searches, and this seems to be what caused Safari to crash. If you’re still having issues, avoiding Safari Suggestions is another way around the bug.

There are two ways to do this. The first is to browse in Private Browsing mode, which causes Safari Suggestions not to be used. Of course, this has its downsides, especially if you frequently visit sites that require you to log in, since you’ll need to log in again every time you return to the site.

A second fix takes slightly more effort, but only slightly: Turn off Safari Suggestions altogether. To do this, simply head to Settings and toggle the Safari Suggestions option off.

Not everyone was affected by the bug, and 9to5 Mac points out that certain data needs to have been cached for the bug to affect you.

Kris Wouk
Former Contributor
Kris Wouk is a tech writer, gadget reviewer, blogger, and whatever it's called when someone makes videos for the web. In his…
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more