7 ms·

I've recently come across a spectacular number of regressions on my M3 Max MacBook Pro, Sequoia as well as previous versions included. The most workflow breaki

I've recently come across a spectacular number of regressions on my M3 Max MacBook Pro, Sequoia as well as previous versions included. The most workflow breaking one (which really tempts me to throw the computer out of the closest window I can find in the room) is a Safari bug that basically randomly fails to open any website with a > Safari can't open the page. The error is: "The operation couldn't be completed. No space left on device" (NSPOSIXErrorDomain:28). Which is embarrassing, as this is a clear regression and it breaks all functionality in the browser - restarting it doesn't fix it, and I need to restart the whole machine for it to _maybe_ get fixed (and it's not really a space issue, both RAM and disk I'm nowhere near their limits).

js2 2y ago
That issue apparently goes back a couple years. https://osxdaily.com/2022/01/28/fix-safari-cant-open-page-nsposixerrordomain28-error-on-mac/ https://osxdaily.com/2022/01/28/fix-safari-cant-open-page-ns... https://old.reddit.com/r/MacOS/comments/qna5js/safari_issue_in_monterey/ https://old.reddit.com/r/MacOS/comments/qna5js/safari_issue_...
fragmede 2y ago
What's your particular use case to keep using Safari if it's not working for you and there are alternatives available?
- dannyw 2y ago
  Not GP, but: iOS Safari dev tools Testing for compatibility
- ReleaseCandidat 2y ago
  The only reason of having a Mac (sorry "real" Mac fans ;) is to be able to test your stuff with MacOS. Especially using Safari and the Iphone and Ipad simulators.
grvdrm 2y ago
I (think) I have a fix for you. 1. Open Activity Monitor 2. Find "Safari Networking" 3. Force quit 4. Refresh Safari tab (that didn't work) Works on M1 MBP w/Sonoma 14.5
- rootsu 2y ago
  Have same issue. The above solution did not resolve the issue. It doesn't bother me much because I mostly use Firefox, but it causes problems when I'm testing front-end stuff on Safari.
  - grvdrm 2y ago
    Bummer. Agree w/workaround solutions. I've just flipped to other browsers for most situations.
a_t48 2y ago
I get this too
deleted 2y ago
[deleted]
concinds 2y ago
Some other things that devs should know about Sequoia: - If you're sticking to Sonoma for stability, be aware Apple doesn't backport all security patches. Apple's release notes show 79 security issues fixed in Sequoia, and only 37 fixed in Sonoma 14.7. Maybe some vulns were only introduced in the Sequoia betas, but based on previous years, that's mostly not the case. Apple only keeps you safe on the latest version. - macOS Sequoia, released days ago, still includes vulnerable years-old binaries like LibreSSL 3.3.6, curl 8.7.1, and python 3.9.6. https://www.intego.com/mac-security-blog/apple-still-leaving-critical-vulnerabilities-unpatched-in-macos-sonoma/ https://www.intego.com/mac-security-blog/apple-still-leaving... (I've tested it's still true on the final 15.0)
- whiterknight 2y ago
  I promise, you will be just fine without the security updates.
  - drawnwren 2y ago
    This is probably misguided. Apple includes the OS version number in the user agent, so an attacker can actually pay to have code delivered only to users with vulnerable versions of MacOS. (advertising marketplaces allow bidding by user agent)
    - threeseed 2y ago
      The user agent is defined by the browser. And it only contains: Intel Mac OS X 10_15_7 irrespective of what Mac you are using.
      - drawnwren 2y ago
        I’m seeing Mozilla/5.0 (Macintosh; Intel Mac OS X 14_7). What do you think the 14_7 stands for on MacOS 14.7?
        koito17 2y ago
xlii 2y ago
I had a very similar issue some time back that was caused by LSP. Long story short I had multiple long running LSPs (fragmented projects) in Emacs that would open many handlers and keep them open. At some point same error started happening and I thought only restart could resolve it. But then I was at the hotel where merely switching network made this issue to appear (I suppose binding was somewhat related to and switch made pool exhaust pool quicker) so I decided to debug it. It turned out that restarting Emacs was enough to close file handlers and resume operations.

js2 2y ago

That issue apparently goes back a couple years. https://osxdaily.com/2022/01/28/fix-safari-cant-open-page-nsposixerrordomain28-error-on-mac/ https://osxdaily.com/2022/01/28/fix-safari-cant-open-page-ns... https://old.reddit.com/r/MacOS/comments/qna5js/safari_issue_in_monterey/ https://old.reddit.com/r/MacOS/comments/qna5js/safari_issue_...

fragmede 2y ago

What's your particular use case to keep using Safari if it's not working for you and there are alternatives available?

dannyw 2y ago
Not GP, but: iOS Safari dev tools Testing for compatibility
ReleaseCandidat 2y ago
The only reason of having a Mac (sorry "real" Mac fans ;) is to be able to test your stuff with MacOS. Especially using Safari and the Iphone and Ipad simulators.

grvdrm 2y ago

I (think) I have a fix for you. 1. Open Activity Monitor 2. Find "Safari Networking" 3. Force quit 4. Refresh Safari tab (that didn't work) Works on M1 MBP w/Sonoma 14.5

rootsu 2y ago
Have same issue. The above solution did not resolve the issue. It doesn't bother me much because I mostly use Firefox, but it causes problems when I'm testing front-end stuff on Safari.
- grvdrm 2y ago
  Bummer. Agree w/workaround solutions. I've just flipped to other browsers for most situations.

a_t48 2y ago

I get this too

deleted 2y ago

[deleted]

concinds 2y ago

Some other things that devs should know about Sequoia: - If you're sticking to Sonoma for stability, be aware Apple doesn't backport all security patches. Apple's release notes show 79 security issues fixed in Sequoia, and only 37 fixed in Sonoma 14.7. Maybe some vulns were only introduced in the Sequoia betas, but based on previous years, that's mostly not the case. Apple only keeps you safe on the latest version. - macOS Sequoia, released days ago, still includes vulnerable years-old binaries like LibreSSL 3.3.6, curl 8.7.1, and python 3.9.6. https://www.intego.com/mac-security-blog/apple-still-leaving-critical-vulnerabilities-unpatched-in-macos-sonoma/ https://www.intego.com/mac-security-blog/apple-still-leaving... (I've tested it's still true on the final 15.0)

whiterknight 2y ago
I promise, you will be just fine without the security updates.
- drawnwren 2y ago
  This is probably misguided. Apple includes the OS version number in the user agent, so an attacker can actually pay to have code delivered only to users with vulnerable versions of MacOS. (advertising marketplaces allow bidding by user agent)
  - threeseed 2y ago
    The user agent is defined by the browser. And it only contains: Intel Mac OS X 10_15_7 irrespective of what Mac you are using.
    - drawnwren 2y ago
      I’m seeing Mozilla/5.0 (Macintosh; Intel Mac OS X 14_7). What do you think the 14_7 stands for on MacOS 14.7?
      - koito17 2y ago

xlii 2y ago

I had a very similar issue some time back that was caused by LSP. Long story short I had multiple long running LSPs (fragmented projects) in Emacs that would open many handlers and keep them open. At some point same error started happening and I thought only restart could resolve it. But then I was at the hotel where merely switching network made this issue to appear (I suppose binding was somewhat related to and switch made pool exhaust pool quicker) so I decided to debug it. It turned out that restarting Emacs was enough to close file handlers and resume operations.