Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Pecka

macrumors 6502
Original poster
Jan 13, 2022
289
252
When I open a new window, browse in it and then close it Safari crashes almost every time for me.

I have tried to disable 1Blocker but that didn't help.

Anyone else having the same problem?
 
  • Like
Reactions: kohanya and 153957
Same problem here, running on macOS 12.7.4 (also on 12.7.5) both Intel and Apple Silicon

Also tried using the old 17.4.1 Safari app, doesn't change anything though, it's using the system's webkit version anyways and the bug seems to be in there.

Console log on closing an affected window:

Code:
default    14:53:53.714431+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::tryClose:
default    14:53:53.716880+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::closePage:
default    14:53:53.790581+0200    Safari    Removing presenter 7BE30965-2064-47BD-8CAB-BBAB006BB05B
default    14:53:53.790668+0200    Safari    Removing presenter 7BE30965-2064-47BD-8CAB-BBAB006BB05B
default    14:53:53.790987+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::close:
default    14:53:53.791578+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791608+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791625+0200    Safari    VideoPresentationManagerProxy::~VideoPresentationManagerProxy(C04B2589)
default    14:53:53.791640+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791655+0200    Safari    VideoPresentationManagerProxy::~PlaybackSessionManagerProxy(C04B2589)
default    14:53:53.791691+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::removeWebPage: webPage=0x7fe615d73a20, pageProxyID=643, webPageID=644
default    14:53:53.791728+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns false (pageCount=0, provisionalPageCount=0, suspendedPageCount=0, m_isInProcessCache=0, m_shutdownPreventingScopeCounter=1)
default    14:53:53.845031+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns true
default    14:53:53.845068+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::setIsInProcessCache(1)
default    14:53:53.845237+0200    com.apple.WebKit.WebContent    0x7f7f2f81d808 - [webPageID=644] WebPage::close:
default    14:53:53.845105+0200    Safari    0x11303f440 - [PID=25560] WebProcessCache::addProcessIfPossible: Checking if process is responsive before caching it
default    14:53:53.846290+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::stopAllLoaders: m_provisionalDocumentLoader=0x0, m_documentLoader=0x12b017000
default    14:53:53.846328+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::stopLoading: m_frame=0x119048370
default    14:53:53.846396+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::stopAllLoaders: Clearing provisional document loader (m_provisionalDocumentLoader=0x0)
default    14:53:53.846693+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::setDocumentLoader: Setting document loader to 0x0 (was 0x12b017000)
default    14:53:53.846832+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::detachFromFrame: m_frame=0x119048370
default    14:53:53.846946+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::stopLoading: m_frame=0x119048370
default    14:53:53.888025+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns false (pageCount=0, provisionalPageCount=0, suspendedPageCount=0, m_isInProcessCache=1, m_shutdownPreventingScopeCounter=0)
default    14:53:53.888942+0200    com.apple.WebKit.WebContent    0x7f7f2f81d808 - [webPageID=644] WebPage::destructor:
default    14:53:53.904356+0200    Safari    0x11303f440 - [PID=25560] WebProcessCache::addProcess: Added process to WebProcess cache (size=3, capacity=30)
error    14:53:53.938889+0200    Safari    Caught exception during runloop's autorelease pool drain of client objects NSInternalInconsistencyException: <private> userInfo: <private>
default    14:53:53.940668+0200    Safari    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An instance 0x6000073217a0 of class NSLayoutGuide was deallocated while key value observers were still registered with it. Current observation info: <NSKeyValueObservationInfo 0x600008c4a360> (
<NSKeyValueObservance 0x600005c78480: Observer: 0x600005c7b1b0, Key path: frame, Options: <New: NO, Old: NO, Prior: YES> Context: 0x600002e93480, Property: 0x60000025d890>
)'
*** First throw call stack:
(
    0   CoreFoundation                      0x00007ff8045376e3 __exceptionPreprocess + 242
    1   libobjc.A.dylib                     0x00007ff8042978bb objc_exception_throw + 48
    2   Foundation                          0x00007ff80532e949 NSKVODeallocate + 534
    3   libobjc.A.dylib                     0x00007ff8042a73ec _object_remove_associations + 589
    4   libobjc.A.dylib                     0x00007ff80428af99 objc_destructInstance + 113
    5   libobjc.A.dylib                     0x00007ff80428af1d _objc_rootDealloc + 62
    6  <…>
 
Last edited:
Same problem here, running on macOS 12.7.4 (also on 12.7.5) both Intel and Apple Silicon

Also tried using the old 17.4.1 Safari app, doesn't change anything though, it's using the system's webkit version anyways and the bug seems to be in there.

Console log on closing an affected window:

Code:
default    14:53:53.714431+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::tryClose:
default    14:53:53.716880+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::closePage:
default    14:53:53.790581+0200    Safari    Removing presenter 7BE30965-2064-47BD-8CAB-BBAB006BB05B
default    14:53:53.790668+0200    Safari    Removing presenter 7BE30965-2064-47BD-8CAB-BBAB006BB05B
default    14:53:53.790987+0200    Safari    0x7fe615d73a20 - [pageProxyID=643, webPageID=644, PID=25560] WebPageProxy::close:
default    14:53:53.791578+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791608+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791625+0200    Safari    VideoPresentationManagerProxy::~VideoPresentationManagerProxy(C04B2589)
default    14:53:53.791640+0200    Safari    VideoPresentationManagerProxy::invalidate(C04B2589)
default    14:53:53.791655+0200    Safari    VideoPresentationManagerProxy::~PlaybackSessionManagerProxy(C04B2589)
default    14:53:53.791691+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::removeWebPage: webPage=0x7fe615d73a20, pageProxyID=643, webPageID=644
default    14:53:53.791728+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns false (pageCount=0, provisionalPageCount=0, suspendedPageCount=0, m_isInProcessCache=0, m_shutdownPreventingScopeCounter=1)
default    14:53:53.845031+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns true
default    14:53:53.845068+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::setIsInProcessCache(1)
default    14:53:53.845237+0200    com.apple.WebKit.WebContent    0x7f7f2f81d808 - [webPageID=644] WebPage::close:
default    14:53:53.845105+0200    Safari    0x11303f440 - [PID=25560] WebProcessCache::addProcessIfPossible: Checking if process is responsive before caching it
default    14:53:53.846290+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::stopAllLoaders: m_provisionalDocumentLoader=0x0, m_documentLoader=0x12b017000
default    14:53:53.846328+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::stopLoading: m_frame=0x119048370
default    14:53:53.846396+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::stopAllLoaders: Clearing provisional document loader (m_provisionalDocumentLoader=0x0)
default    14:53:53.846693+0200    com.apple.WebKit.WebContent    0x119055540 - [pageID=644, frameID=2, isMainFrame=1] FrameLoader::setDocumentLoader: Setting document loader to 0x0 (was 0x12b017000)
default    14:53:53.846832+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::detachFromFrame: m_frame=0x119048370
default    14:53:53.846946+0200    com.apple.WebKit.WebContent    0x12b017000 - [pageID=644, frameID=2, isMainFrame=1] DocumentLoader::DocumentLoader::stopLoading: m_frame=0x119048370
default    14:53:53.888025+0200    Safari    0x11330e340 - [PID=25560] WebProcessProxy::canTerminateAuxiliaryProcess: returns false (pageCount=0, provisionalPageCount=0, suspendedPageCount=0, m_isInProcessCache=1, m_shutdownPreventingScopeCounter=0)
default    14:53:53.888942+0200    com.apple.WebKit.WebContent    0x7f7f2f81d808 - [webPageID=644] WebPage::destructor:
default    14:53:53.904356+0200    Safari    0x11303f440 - [PID=25560] WebProcessCache::addProcess: Added process to WebProcess cache (size=3, capacity=30)
error    14:53:53.938889+0200    Safari    Caught exception during runloop's autorelease pool drain of client objects NSInternalInconsistencyException: <private> userInfo: <private>
default    14:53:53.940668+0200    Safari    *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An instance 0x6000073217a0 of class NSLayoutGuide was deallocated while key value observers were still registered with it. Current observation info: <NSKeyValueObservationInfo 0x600008c4a360> (
<NSKeyValueObservance 0x600005c78480: Observer: 0x600005c7b1b0, Key path: frame, Options: <New: NO, Old: NO, Prior: YES> Context: 0x600002e93480, Property: 0x60000025d890>
)'
*** First throw call stack:
(
    0   CoreFoundation                      0x00007ff8045376e3 __exceptionPreprocess + 242
    1   libobjc.A.dylib                     0x00007ff8042978bb objc_exception_throw + 48
    2   Foundation                          0x00007ff80532e949 NSKVODeallocate + 534
    3   libobjc.A.dylib                     0x00007ff8042a73ec _object_remove_associations + 589
    4   libobjc.A.dylib                     0x00007ff80428af99 objc_destructInstance + 113
    5   libobjc.A.dylib                     0x00007ff80428af1d _objc_rootDealloc + 62
    6  <…>
I have the same problem, Safari 17.5 and OS 12.7.5. If I close a Safari window I get an error message for uncaught exception. It still malfunctioned in Safe Boot. I deleted all extensions but the problem persisted. One by one I removed any support files connected with Safari whether in Preferences or in Containers as well as Login Daemons. I ultimately reinstalled the OS which installed Safari 15 which worked. When I updated to Safari 17.5 the problem returned. Tried new user and didn't have the problem. I opened a case with Apple and sent them the alert, the error message and the report.
 
  • Like
Reactions: kohanya
Can report the same behaviour for Safari 17.5 on Monterey 12.7.5.

I have updated a few other Macs here, the others are on Ventura and Sonoma, all of which have no such issue. It only happens with Monterey
 
No crashes for me (Safari 17.5 on macOS 12.7.5 & 14.5), but I guess it might have something to do with the settings for Homepage and “New windows open with”. I have both set to a local html file.

You could try changing them temporary to something else then currently set.

Change your home page in Safari on Mac https://support.apple.com/guide/safari/ibrw1020/mac
Weird bug in Safari after 14.5 update https://forums.macrumors.com/threads/weird-bug-in-safari-after-14-5-update.2426234/
I don't think the start page has much to do with it. On my setup the crashing always happens upon closing a tab / window. And I tried your suggestion in changing the Safari setting of opening new windows with empty page, makes no difference.

I am inclined to suspect the issue is with how Safari tries to save or upload certain things upon closing, like for iCloud tabs or synced history. But the crash log doesn't show signs of that.
 
Has anyone found a temporary solution yet? My Safari was crashing 15 times a day, sometimes the crash happen right after Safari relaunch, it is so fast even the crashlog doesn't appear in console.

This is on a main workstation Mac Studio, I purposely held on to Monterey due to stability and relatively free of newer macOS issues. I am seriously pondering if I should move on to at least Ventura just because of this Safari problem.
 
  • Like
Reactions: kohanya
Update, in case this helps anyone:

Safari stays crashing today, driving me absolutely nuts and down with my productivity.
Found out:
1) you cannot downgrade by just trashing Safari 17.5, by copying or installing 17.4.1
2) you must downgrade macOS to a previous version where Safari was bundled with an earlier version
3) this macOS downgrade cannot happen by just a direct re-install, you have to wipe and start from scratch / Time Machine backup

At this point I gave up, not being able to browse the web is essentially crippling my work. (I could use Chrome but all my cloud tabs etc are in Safari)

So I bite the bullet and upgraded to Ventura.
Despite some known software incompatibility, printer driver / profile issues, at least those problems are already known and I can deal with them.
The Safari that came with the Ventura install (from AppStore) actually stays at 16.6, to my pleasant surprise. I am going to stick with this for as long as I can.
I have another MBP2015 15" that's stuck with Monterey, luckily I hadn't got that machine to 12.7.5 / Safari 17.5, this will also stay clear.

So much for modern Apple software quality.
 
Downgrading Safari is possible without too much trouble, it takes some time though. You cannot do it directly, but need to reinstall macOS in order to reset the System Volume (including Webkit/Safari) to an earlier state. You may need to create a bootable installer for macOS (not sure whether using recovery mode works as well. I already had a bootable installer for 12.7.4 ready on a thumb drive anyways, so I used that) Then just boot that and install macOS on the current volume (your personal data won't be deleted, it just resets the system volume) Afterwards you can upgrade to the newest version 12.7.5 (if your bootable installer is not already on that version), but obviously avoid the Safari update (make sure it does not get installed automatically) and instead install the previous Safari version via the updater from here:
https://swcdn.apple.com/content/dow...tggnknxt40s9rz2d/Safari17.4.1MontereyAuto.pkg

Takes some time as all the files need to be copied to the system volume again, but otherwise the experience of reinstalling that way is not really different from installing a macOS upgrade.

@Cancha
If you're already on Ventura, downgrading to Monterey is probably not an option anymore, though you don't need to stick with Safari 16.6, but can also install the previous Safari/Webkit version manually:
https://swcdn.apple.com/content/dow...2re99l9qbpofbvi3k/Safari17.4.1VenturaAuto.pkg

Although the issue with 17.5 seems to only appear on Monterey, so just updating Safari on Ventura or Sonoma might be safe anyways.
 
  • Like
Reactions: Chancha
Downgrading Safari is possible without too much trouble, it takes some time though. You cannot do it directly, but need to reinstall macOS in order to reset the System Volume (including Webkit/Safari) to an earlier state. You may need to create a bootable installer for macOS (not sure whether using recovery mode works as well. I already had a bootable installer for 12.7.4 ready on a thumb drive anyways, so I used that) Then just boot that and install macOS on the current volume (your personal data won't be deleted, it just resets the system volume) Afterwards you can upgrade to the newest version 12.7.5 (if your bootable installer is not already on that version), but obviously avoid the Safari update (make sure it does not get installed automatically) and instead install the previous Safari version via the updater from here:
https://swcdn.apple.com/content/dow...tggnknxt40s9rz2d/Safari17.4.1MontereyAuto.pkg

Takes some time as all the files need to be copied to the system volume again, but otherwise the experience of reinstalling that way is not really different from installing a macOS upgrade.

@Cancha
If you're already on Ventura, downgrading to Monterey is probably not an option anymore, though you don't need to stick with Safari 16.6, but can also install the previous Safari/Webkit version manually:
https://swcdn.apple.com/content/dow...2re99l9qbpofbvi3k/Safari17.4.1VenturaAuto.pkg

Although the issue with 17.5 seems to only appear on Monterey, so just updating Safari on Ventura or Sonoma might be safe anyways.
Thank you for the detailed response, yeah I already moved on to Ventura, but I will keep those in mind for the next problem. I figured it might be somewhat possible to downgrade piece by piece like you suggested, but at the same time I also realize it may be time to move on; I specifically tried to avoid a Ventura+ printer profile issue that affects a lot of graphic / print workflow, which by now is already well known and have workarounds even in Ventura / Sonoma. I feel more comfortable dealing with that than staying and hoping Apple doesn’t break the next thing.

I just feel like this won’t be the last issue Monterey is going to get, Apple seems to be on a track to break older things sooner than they stops supporting them.
 
I just feel like this won’t be the last issue Monterey is going to get, Apple seems to be on a track to break older things sooner than they stops supporting them.
I can't help but wondering if this is Apple's strategy to force people to replace their old machine with a new one? :(

I am very affected by this issue because I'm still using a 2017 MBA which is running on Monterey. I feel very reluctant to churn out money for a new machine because my MBA still works perfectly fine for me. Why would I need a newer machine if this is enough and still totally working fine?

It's Apple's updates that make it NOT working as fine anymore :(

I used to be able to edit Cinematic video files from my iPhone 13 in my MBA (with Monterey) before. Then Apple updated iMovie, and I have to update to Sonoma if I want to do the exact same thing. But my old machine isn't supported. Why?

Safari was working great. Then Apple updated it to 17.5 and it broke. And it only happened in Monterey? So I have to update to Sonoma? So I have to buy a new machine to have a functioning Safari?
 
  • Like
Reactions: hooptyuber
When I open a new window, browse in it and then close it Safari crashes almost every time for me.

I have tried to disable 1Blocker but that didn't help.

Anyone else having the same problem?
exactly the same issue. safari crashes when i close a tab either by alt+w or x icon mouse.
safari 17.5 (17618.2.12.111.5)
very unstable. sometimes it works even after closing 20+ tabs. sometimes crashes repeatedly.
it started after 12.7.5 update monterey.
 
Last edited:

Safari 17.5 crashes after dismissing peeked links. macOS Monterey 12.7.5​

link peeking feature of safari makes safari crash everytime on my safari 12.7.5
its a 3 finger tap on a link in a webpage.
 

Safari 17.5 crashes after dismissing peeked links. macOS Monterey 12.7.5​

link peeking feature of safari makes safari crash everytime on my safari 12.7.5
its a 3 finger tap on a link in a webpage.
In this case the peeping part probably has nothing to do with it, as it literally is opening a webpage just not displaying it full size for you yet. The bug seems to be an in-engine issue, so.
 
In this case the peeping part probably has nothing to do with it, as it literally is opening a webpage just not displaying it full size for you yet. The bug seems to be an in-engine issue, so.
everything is related. so you do not have the link peeking crashes?
 
everything is related. so you do not have the link peeking crashes?
I guess I chose the wrong words; peeping is related, but since the issue also happens without peeping, it quite clearly isn't the culprit. And as mentioned, the issue seems Safari rendering engine or network related.
 
Same problem with Safari crashing as reported by earlier comments. Running Safari 17.5 on macOS Monterey 12.7.5. I am using a late 2015 27" 5K iMac, 4GHz i7, 32GB RAM, AMD Radeon R9 M395X 4GB, and Apple 1TB internal SSD.
 
I have the same problem on my MacBook Pro mid-2015 Retina. I use macOS Monterey 12.7.2 and never had any major browser issues until I updated to Safari 17.5, which crashes when I close a window, or a window including multiple opened tabs.


I read on Reddit and other sites that some people have reinstalled the operating system and downloaded an older version of Safari. I would prefer to avoid this route, if possible to find a quicker fix.

I tried to fix the problem by restarting the Mac in Safe Mode and let the machine work for around 20 - 25 minutes.

After that, I restarted the computer and used Safari for about an hour with no crashes at all. Same the day after.

Unfortunately the crashes started again two days later and I am not sure what is triggering them, so restarting in safe mode didn't resolve the issue.

MAC SPECS:

Safari Version 17.5
MacBook Pro Retina Mid 2015
macOs Monterey 12.7.2
Processor: 2.8 GHz Quad-Core Intel Core i7

If anybody know a possible solution without having to reinstall the OS it would be great.
 
I am fed up with Safari 17.5 crushing all the time, as it causes me a huge waste of time and money at work.

Any suggestions on what is the best browser to use on MacBook Pro?


MAC SPECS:
MacBook Pro Retina Mid 2015
macOs Monterey 12.7.2
Processor: 2.8 GHz Quad-Core Intel Core i7
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.