Safari issue on M1 Mini/Monterey

[Cave Man]

Running Monterey on my Mac mini M1 and whenever the computer sleeps, Safari is non responsive for web sites after wake. This is the message I get:

Safari Can’t Open the Page
Safari can’t open the page. The error is: “The operation couldn’t be completed. No space left on device” (NSPOSIXErrorDomain:28)

My boot drive has 400 GB+ available and I see no memory problems in Activity Monitor. The only solution is to quit and relaunch Safari, then all returns to normal. Any ideas what might be occurring?

 

[K two]

Running Monterey on my Mac mini M1 and whenever the computer sleeps, Safari is non responsive for web sites after wake. This is the message I get:

Safari Can’t Open the Page
Safari can’t open the page. The error is: “The operation couldn’t be completed. No space left on device” (NSPOSIXErrorDomain:28)

My boot drive has 400 GB+ available and I see no memory problems in Activity Monitor. The only solution is to quit and relaunch Safari, then all returns to normal. Any ideas what might be occurring?

The Monterey which came on the Mac mini M1 or 12.0.1?

 

[weirdsmith]

I ran into this after upgrading to Monterey 12.0.1 from Big Sur. Unchecking "Hide IP address from trackers" in the Privacy tab of Safari preferences seems to work. You shouldn't need to restart Safari. I just switch it off and the problem goes away immediately for me.

Seems to be a Monterey bug as the Safari version (15.1) is unchanged from Big Sur.

 

[Cave Man]

I ran into this after upgrading to Monterey 12.0.1 from Big Sur. Unchecking "Hide IP address from trackers" in the Privacy tab of Safari preferences seems to work. You shouldn't need to restart Safari. I just switch it off and the problem goes away immediately for me.

Seems to be a Monterey bug as the Safari version (15.1) is unchanged from Big Sur.

OK, I have unchecked it and will see how it goes. Seems like something I would prefer to have checked, though. Hopefully, Apple will fix this issue soon. Thanks much.

 

[weirdsmith]

No worries. Hope it works for you.

I thought I would check it again now that I'm running 12.1 & Safari 15.2 and the bug is still there, though the behaviour seems slightly different than before. Previously the problem seemed to go away immediately the checkbox was unchecked. When I tested it today I had to restart Safari to get it to load webpages again.