[NewsPoster]

On Tuesday, Apple released a final version of 10.11.3, the third free update to OS X El Capitan. The focus of the update, which has no noticeable interface changes or new features, is said to be on the "stability, compatibility, and security of your Mac," according to Apple's release notes. The latest update was in beta since last month, and briefly shared beta status with the next update, 10.11.4, which is currently being tested by developers. The 10.11.3 update is available exclusively through the software update section of the Mac App Store.

Apple's notes on the release include unspecified bug fixes and security updates, along with the usual performance and stability improvements. In all, the update received three beta releases, and as mentioned a 10.11.4 update is in the works, likely to be released in the same time frame as iOS 9.3, which is also currently in beta.

[Inkling]

The usual headaches with these downloads. Try, try, and try again. Why does Apple release both OS X and iOS updates on the same day? And why can't failed downloads resume where they stopped? There was software in the 1980s that could do that.

[Mike Wuerthele]

While I've got some fearless staffers, I generally let other people collate failure reports and incompatibilities for a day or two before I jump.

[Charles Martin]

I had no trouble at all downloading the update.

[bobolicious]

...mine went to server & seeded upgrades in minutes...
Sometimes Applethings work with exceptional ease, for the rest of us...
A Pandora's box of faith in tech...

[Charles Martin]

I decided to test Inkling's contention that downloads from the MAS can't resume. Downloaded a third of the OS X update in a coffeeshop on a slow connection, went home, finished the download in a couple of minutes. Picked up exactly where it had left off.

[Charles Martin]

Update to my previous post: it did resume, but choked on the installation, so automatically went back to the store and re-downloaded the whole thing. So yes, it appears an interrupted download (which could happen to rural users or people who walk out of Wi-Fi range halfway through) will need to be restarted over again as an anti-corruption measure. Other (Safari) downloads can resume, but it's probably for the best that one that messes with your OS install has to be wholly intact to avoid a broken install.

I think that ought to be reported. If 100 million OS X users try to download OS X and get partial downloads due to Apple's server loads, then that means a lot of corrupted install files, and lots of re-downloads, which means more server load... and still more frustrated users who think "OS X broke my Mac"

[Spheric Harlot]

Isn't an automatic update that just works - whether by re-downloading or not - simply an automatic update that just works?

Nothing is breaking for anybody.

10.11.3 still has the annoying "inactive window key execution" bug where, sometimes, if you are in a tab in Safari, and you click into a TextEdit window, then you press Command-W to close it, instead of closing the TextEdit window, it closes the Safari tab. This problem just seems to be randomly occurring, but happens maybe 1 out of 25 times. This is a very frustrating and still annoying bug that wasn't even in the 10.11 betas.

[Flying Meat]

Hey, that's nice. The KB article is up at the same time!

And Reminders still doesn't stay organized. When I update one of my lists and move items around and/or add items, then close Reminders, then re-open Reminders, my items are all shuffled around in a random order.

But even more serious, 10.11.3 still has a serious bug where the GPU crashes after watching just a couple YouTube videos, causing Safari to freak out and you have to restart the computer to remedy this issue.

[Mike Wuerthele]

Originally Posted by And.reg 

But even more serious, 10.11.3 still has a serious bug where the GPU crashes after watching just a couple YouTube videos, causing Safari to freak out and you have to restart the computer to remedy this issue.

Do you have a link to an Apple Community Support Forum thread for this one? I've never even heard of this one, or seen it manifests itself.

No, but I'm not surprised, since it just seems to happen randomly, but I've seen it happen maybe 10 times in the last few months. So it's not frequent... I'm on a 2015 Pro Macbook, with just Intel's Iris Pro GPU, no dGPU.

What happens is, as you finish up watching a video in a Safari tab, you press Command-W to close it. Usually, Safari jumps back to a tab and you can just get back to doing whatever. But sometimes, Safari, and the entire rest of the computer, just hangs for like 30 seconds, and the entire computer seems to just become very slow with loading anything graphically thereafter.

[Mike Wuerthele]

Huh. Okay. I'll see what I can find out.

Originally Posted by Mike Wuerthele 

Do you have a link to an Apple Community Support Forum thread for this one? I've never even heard of this one, or seen it manifests itself.

Here you go, Mike, a link to an Apple Community Support Forum thread for this issue (actually a link to a specific post, not authored by me or anyone who I would know):

https://discussions.apple.com/message/29440022#29440022

It appears to be depreciated and/or misprogrammed code within Safari concerning the playback on HTML5 video , and might not be a GPU-specific bug. (Though I have seen, in the console, GPU restarting on issues with similar UI behavior.)

Also a possibly related thread: https://discussions.apple.com/thread...art=0&tstart=0

[...12 days later...]

This is still happening, the "GPU crash"-like happens if I, say, have a browser window on a YouTube video, after I have been using Safari for a while, the behavior discussed in the threads above happens to me.

[Mike Wuerthele]

We've been a bit busy, I haven't had much of a chance to look into it. It's on the Whiteboard of Doom, though.