You open a page in Safari on your Mac, it flashes, goes blank, and a gray notice appears: “This webpage was reloaded because a problem repeatedly occurred.” Reload it and the same thing happens — a loop. It looks alarming, but this is one of Safari’s most fixable errors, and it almost never means your Mac is broken.
What “a problem repeatedly occurred” actually means
Safari runs each tab in its own web-content process (WebKit) so one bad page can’t take down the whole browser. When that per-tab process crashes several times in a row, Safari stops retrying and shows the “problem repeatedly occurred” message instead of looping forever. In plain terms: one specific page or tab is crashing, not Safari and not your Mac.
The usual triggers, most common first:
- A content blocker or extension that mangles the page’s scripts.
- Corrupt cached data or cookies for that one site.
- A page that’s using too much memory (heavy web app, runaway ad script).
- An experimental WebKit feature you toggled on in the Develop menu.
- Occasionally, low free RAM or storage on the Mac itself — the honest part is at the bottom.
The fixes, fastest first
1. Reload once, then close and reopen the tab
Press Cmd‑R to reload. If the loop continues, don’t keep hammering reload — close the tab entirely (Cmd‑W) and open the site in a fresh tab. A brand‑new web‑content process clears a one‑off crash. If a fresh tab loads fine, you’re done.
2. Try the page in a Private window
Open File › New Private Window (Cmd‑Shift‑N) and paste the URL. A Private window ignores your extensions and most cached site data. If it loads there but not normally, the cause is an extension or that site’s stored data — fixes 3 and 4 below.
3. Disable content blockers and extensions
This is the number‑one cause. Go to Safari › Settings › Extensions and untick every extension (especially ad/content blockers), then reload the page. If it works, turn them back on one at a time until the culprit reappears — then leave that one off for the site, or check its settings for a per‑site allow list.
4. Clear this one site’s data — not everything
You don’t need to wipe all of Safari. Go to Safari › Settings › Privacy › Manage Website Data…, search the site’s name, select it, and click Remove. That deletes only that site’s cookies and cache, so you stay logged in everywhere else. Reload the page afterward. If you’d rather understand the difference between per‑site data and a full cache wipe, our guide to clearing the cache on a Mac walks through both.
5. Turn off experimental WebKit features
If you’ve ever enabled the Develop menu and flipped experimental features on, one of them can crash real pages. Go to Safari › Settings › Advanced, tick Show features for web developers, then open the Develop › Feature Flags (or Experimental Features) menu and reset anything you changed back to its default. When in doubt, turn them all off.
6. Check whether the page is eating memory
A single heavy page (or a runaway ad) can starve its own tab. Open Activity Monitor (Spotlight → “Activity Monitor”), sort the Memory tab, and look for a Safari Web Content process using an unusually large amount. Quit that process (it only closes the offending tab) and reopen the site. Closing other memory‑hungry apps first gives the page more headroom.
7. Update macOS and restart
Safari ships with macOS, so its WebKit engine is only as current as your system. Go to System Settings › General › Software Update, install anything pending, and restart. A reboot also clears any stuck web‑content processes in one shot. If the same page still loops after a fresh restart, move on to the hardware check.
Still looping? It might be Safari-wide, not one page
If every site throws the error — not just one — the problem is broader than a single tab. That usually overlaps with general loading failures, so work through our Safari slow or pages not loading fix‑in‑order guide. If pages fail with a security or certificate warning instead, see Safari “cannot establish a secure connection.”
The honest part: when it’s the Mac, not the page
Repeated web‑content crashes across many sites — paired with spinning beachballs, fans ramping, or the whole Mac freezing — can point at failing RAM, a dying SSD, or an aging Intel Mac that’s simply out of headroom. If a clean restart, an updated macOS, and a fresh user profile all still loop, the browser is just the messenger.
At that point it’s worth pricing a replacement rather than chasing the crash. A refurbished Apple‑silicon MacBook handles modern, script‑heavy pages without breaking a sweat, and you can start on our Apple clearance deals to see how affordable a reliable upgrade is. If your current Mac still powers on, its parts have value — get a trade‑in quote and put that credit toward the new one.
Frequently asked questions
What does “A problem repeatedly occurred” mean in Safari?
It means the web‑content process for that one tab crashed several times in a row, so Safari stopped auto‑reloading it. It’s a per‑tab crash — not a sign that Safari or your Mac is broken.
Why does only one website give me this error?
That site’s scripts, cached data, or an extension acting on it are crashing the tab. Clearing just that site’s data (Safari › Settings › Privacy › Manage Website Data) or disabling extensions fixes the large majority of single‑site cases.
Will fixing this delete my bookmarks or passwords?
No. Reloading a tab, disabling extensions, and removing one site’s data leave your bookmarks, saved passwords, and history untouched. You’d only lose that one site’s cookies, meaning you may need to log back in there.
The error happens on every site — what now?
A Safari‑wide loop usually means low free RAM, a stuck system process, or a macOS issue. Restart, install any macOS update, and work through the Safari not loading guide. If it persists across a fresh restart, suspect the Mac’s memory or storage.
Is a Mac that keeps crashing web pages worth replacing?
If browsing is unusable even after a clean macOS and reset, an older or failing Mac is often the cause. A refurbished Apple‑silicon model fixes it for good — check clearance pricing, and trade in the old one to offset the cost.