Uh oh Significant Memory problem on Safari!
So Hi There I went on a Safari it says This webpage was reloaded because it was using significant memory thats too much!
iMac 27″, macOS 10.13
The Apple Support Community will permanently close on November 20, 2026. Starting today, the site will no longer accept new posts and is available in a read-only state.
You can continue to find trusted guidance and support on the official Apple Support site.
We want to thank the community members who have contributed their time and expertise to help others with their Apple products.
The Apple Support Community will permanently close on November 20, 2026. Starting today, the site will no longer accept new posts and is available in a read-only state.
You can continue to find trusted guidance and support on the official Apple Support site.
We want to thank the community members who have contributed their time and expertise to help others with their Apple products.
So Hi There I went on a Safari it says This webpage was reloaded because it was using significant memory thats too much!
iMac 27″, macOS 10.13
Go step by step and test.
1. Update Safari, if an update is available. Update may come with bug fixes.
https://support.apple.com/en-us/HT204416
https://support.apple.com/en-us/HT201541
2. Quit Safari, launch Safari holding the Shift key down.
https://support.apple.com/en-us/HT203987
3. Startup in Safe Mode. https://support.apple.com/guide/mac-help/start-up-your-mac-in-safe-mode-mh21245/mac.
Quote:
It also does a basic check of your startup disk, similar to using First Aid in Disk Utility.
And it deletes some system caches, including font caches and
the kernel cache, which are automatically created again as needed.
4. Clear History
https://support.apple.com/guide/safari/clear-your-browsing-history-sfri47acf5d6/mac
Please read the article before clearing history,
this is like a low level resetting of Safari without affecting passwords and bookmarks.
5. If Safari doesn't open a webpage or isn’t working as expected
Uh oh Significant Memory problem on Safari!