Update to 12.6.5 and/or Safari 16.4.1 (17615) Causing Corrupted jpegs on websites?

[BuddyRich]

Its not universal but I am getting corrupted jpegs on some websites after the 12.6.5 updates and/or 16.4.1 Safari update.

Not all websites and not even all jpegs on the page, but many times jpegs are displaying half or more complete with the rest full of static (like from an OTA TV without a signal - though sometimes kinda like interlaced scan lines). UI elements (that are joegs or other formates themselves) from the same site display fine, and right clicking and displaying the corrupt image in its own tab is fine. Kinda like it half loaded. Its odd

I thought it might have been an Apple silicon thing but it happens on both my Mac Studio with M1 Max and a 2018 Intel Mac. No issues with Safari on iOS or iPad OS... just Mac OS after the latest update to it and the latest Safari update.

I do run AdGuard plugin/extension but even with it disable it does it.

The specific site it does it most often on is www.cbc.ca for me... the man story photo is usually corrupted but the rest of the sites UI elements are fine.

 

[bogdanw]

I haven’t seen on other sites, but on that one, yes. It’s not consistent, sometimes the image loads corectly, sometimes it loads after a page refresh.

 

[BuddyRich]

I haven’t seen on other sites, but on that one, yes. It’s not consistent, sometimes the image loads corectly, sometimes it loads after a page refresh.
View attachment 2191655

That is exactly what I am seeing (and something its looks like static).

It could be something with the CMS that CBC is using, but for whatever reason its only done it since the last update to Mac/Safari.

 

[bogdanw]

I thought of a CDN too, but the image always opens corectly with right-click open image in new ..
The page uses img loading="lazy" that might not be supported by Safari
https://www.w3schools.com/tags/att_img_loading.asp

 

[BuddyRich]

I thought of a CDN too, but the image always opens corectly with right-click open image in new ..
The page uses img loading="lazy" that might not be supported by Safari
https://www.w3schools.com/tags/att_img_loading.asp

You might be onto something with the lazy tag...

I just had the same issue on the ikea website.

and looking at the HTML for the image:

<img class="pub__image" alt="A woman sits on a broad window sill and looks out at a misty day, while rugged up with a blanket, cushion and cup of tea." src="https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=s" srcset="https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=sg 1600w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xxxl 1400w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xxl 950w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xl 800w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=l 750w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=m 600w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=s 500w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xs 400w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xxs 300w,
  https://www.ikea.com/ext/ingkadam/m/1981e371957efb06/original/PH186380-crop005.jpg?f=xxxs 240w" sizes="(min-width: 56.25em) 78vw, 100vw" loading="lazy">

It also uses the lazy tag. I guess why is this an issue all of the sudden. I am sure these sites used the tag before, and its only the latest version of safari that has this issue (and only on Mac, I can't reproduce this on mobile Safari...)

 

[bogdanw]

Well ...
Safari 16.4 CVE-2023-27932 "Processing maliciously crafted web content may bypass Same Origin Policy"
https://support.apple.com/en-us/HT213671
Safari 16.4.1 CVE-2023-28205 "Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been actively exploited."
https://support.apple.com/en-us/HT213722

 

[Lloyd Detroit]

I'm having the identical problem when viewing the online version of The Washington Post: Distorted images, as well as photos appearing on the wrong articles. I've been dealing with the WAPO Problems people for months, trying all sorts of "fixes", to no avail. They just sent a link to this page. Like others here, the issue stated after the latest IOS update. The problem ONLY occurs on my MacBook, not my iPad or iPhone. The issue does not occur when using Chrome. I don't see any solutions here. Is there one?

 

[bogdanw]

What might help:
- disabling iCloud Private Relay https://support.apple.com/en-us/HT212614 and Hide IP address https://support.apple.com/guide/safari/privacy-sfri35610/mac to speed up browsing

- Develop menu - Experimental Features – disabling Lazy iframe loading and Lazy image loading
https://support.apple.com/guide/safari/use-the-developer-tools-in-the-develop-menu-sfri20948/mac

 

[Lloyd Detroit]

Thanks, Bogdanw. I followed the recommended changes, but the issue persists on the Washington Post website. Unless I can find another fix, I'll be using Chrome to access it.

 

[mikegem]

What might help:
- disabling iCloud Private Relay https://support.apple.com/en-us/HT212614 and Hide IP address https://support.apple.com/guide/safari/privacy-sfri35610/mac to speed up browsing

- Develop menu - Experimental Features – disabling Lazy iframe loading and Lazy image loading
https://support.apple.com/guide/safari/use-the-developer-tools-in-the-develop-menu-sfri20948/mac

View attachment 2199533

Disabling Lazy Image loading fixed this issue on all the sites I've seen it, including WAPO. Thanks!

 

[Lloyd Detroit]

Disabling Lazy Image loading fixed this issue on all the sites I've seen it, including WAPO. Thanks!

Yes, it's working fine now on Safari. Thanks, Bogdanw

 

[Lloyd Detroit]

Yes, it's working fine on Safari now. Thanks, Bogdanw!

 

[MJPinSF]

I disabled the 2 Lazy features, emptied my Safari cache, shut down and restarted, and it's still doing it on the Washington Post and National Geographic websites

 

[Lloyd Detroit]

I disabled the 2 Lazy features, emptied my Safari cache, shut down and restarted, and it's still doing it on the Washington Post and National Geographic websites

View attachment 2204978


View attachment 2204975

MJP, go back to the “Develop” drop down & make sure those Lazy features haven’t defaulted back.

 

[bogdanw]

With Safari closed, from Terminal:
- check if the values have been saved

defaults read ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyImageLoadingEnabled
defaults read ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyIframeLoadingEnabled

Both should return 0 (zero) for disabled and 1 for enabled.

- disable Lazy Image Loading and Lazy iframe loading

defaults write ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyImageLoadingEnabled -bool NO
defaults write ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyIframeLoadingEnabled -bool NO

- enable Lazy Image Loading and Lazy iframe loading

defaults write ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyImageLoadingEnabled -bool YES
defaults write ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyIframeLoadingEnabled -bool YES

Terminal might require Full Disk Access to execute the commands
"Change Privacy & Security settings on Mac" https://support.apple.com/guide/mac-help/change-privacy-security-settings-on-mac-mchl211c911f/mac

 

[MJPinSF]

MJP, go back to the “Develop” drop down & make sure those Lazy features haven’t defaulted back.

They haven't. I've checked several times.

 

[MJPinSF]

With Safari closed, from Terminal:
- check if the values have been saved

defaults read ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyImageLoadingEnabled
defaults read ~/Library/Containers/com.apple.Safari/Data/Library/Preferences/com.apple.Safari.plist WebKitExperimentalLazyIframeLoadingEnabled

Both should return 0 (zero) for disabled and 1 for enabled.

[SNIP]

Both returned "0" and the problem continues:

 

[derekww]

Same problem here, most commonly seen on cbc.ca but certainly on other sites as well. I contacted CBC tech support and they just said use Chrome, or try empty cache, cookies, etc., which I tried but did not correct the problem. I'm on 12.6.5 and 16.4.1, M1, AdGuard.

Anyone see this problem either occur or resolved on macOS 12.6.6 and Safari 16.5?

 

[MJPinSF]

Same problem here, most commonly seen on cbc.ca but certainly on other sites as well. I contacted CBC tech support and they just said use Chrome, or try empty cache, cookies, etc., which I tried but did not correct the problem. I'm on 12.6.5 and 16.4.1, M1, AdGuard.

Anyone see this problem either occur or resolved on macOS 12.6.6 and Safari 16.5?

It's still happening here, Washington Post, v.16.5:

 

[derekww]

Same problem after updating to 12.6.6. and 16.5, even after disabling the 2 lazy features.

 

[SketchyClown]

Make sure you dump your cache and cookies for the site. It kept doing it on the CBC until I did that and reopened Safari.

 

[MJPinSF]

Make sure you dump your cache and cookies for the site. It kept doing it on the CBC until I did that and reopened Safari.

I've done that numerous times, to no avail. And just tried again.The result:

:

 

[SketchyClown]

I've done that numerous times, to no avail. And just tried again.The result:

View attachment 2209974 :

Yeah seemed to cure it here for awhile, but now it's back to being corrupted again. Blah.

 

[ckuwajima]

Hi, had same problem with Safari 16.5, MacOS 12.6.6. Disabling both, Lazy iframe loading and Lazy image loading, did not solve the problem.

Disabling "GPU Process: Canvas redering" and "GPU Process: DOM rendering" in Safari->Develop->Experimental Features solved the image corruption.

 

[MJPinSF]

That seems to have worked (for now, lol). Thanks!

(Remember to clear cache and cookies, though.)