Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The Meltdown update was early December.

For 10.13 it was, but it isn’t clear that it was for 10.12 or 10.11. Because Apple said it was in their security document, but then they removed the reference to Meltdown except for 10.13.
 
really regret upgrading to high sierra. 50% of the time when i open up my MBP the battery is dead because it decided to not go to sleep when i closed the lid
 
Regarding HIgh Sierra complaints, the only one I have is that my Mac Pro doesn’t always go to sleep on its own, but since I’m running on unsupported hardware (flashed cMP 4,1), I can’t really say if that one is on Apple. Otherwise, it has been just fine.

This would potentially go all the way back to the Power Mac x500 computers from 1995.
Yeah, eventually they have to draw a line in the sand on old hardware. Many times it’s not just because the device has become more rare, but also because the vendor supplying the components has also dropped support. GPU architectures alone have changed substantially, so things like OpenCL support are just impossible. Designing modern software around such old hardware gets you Windows, which does a decent enough job, but it’s why things like font scaling on high-DPi displays are still such a mess. Too much legacy support can often result in a bad user experience.
 
FWIW, it's a hardware issue with Intel, not Apple. Windows & Linux are just as affected by this as Apple.
he was talking about general issues of High Sierra not these Intel problems.
[doublepost=1515445614][/doublepost]
Can you provide a specific list of these bugs and performance issues.
living example of the performance issues is the Mac in front of you.if you don't feel it good for you, but he,I and many others are feeling the poor performance of High Sierra.I have a top of the range 12" MacBook of 2016,and it's noticeably slower and laggier than before just because of this awful High Sierra.
 
It’s likely addressed at the JavaScriptCore level, so system-wide.

I also read that browsers were addressing the issue by removing a feature from JavaScript.

There's isn't any "Javascript Core" in MacOS. Each browser brings it's own Javascript implementation on MacOS.

You might be thinking of iOS, where all browsers have to use the Safari-based UIWebView or WKWebView framework, and browsers are not allowed to use their own rendering or Javascript engines.
 
Can't wait to see the benchmarks!

as a newer MAC user who bought into Apple's suggestion that their 5400 rpm drives were implemented in a way that didn't suck - I doubt my system can get any slower.

(Yes - apple - your 5400 rpm drives suck as bad as they did in PC' 10 or more years ago.) And you've made it pretty hard to replace it with a blade ssd. - I guess I should be happy you didn't solder the old chugger in to save yourself 25 cents on the cable.
 
Last edited:
Lol I'm not getting High Sierra. PoS full of bugs and performance issues.

Keep believing that, if you need to.
[doublepost=1515446645][/doublepost]
Interestingly ... this update appears to have updated the OS X kernel itself. Note the output of SW_VERS on the command line pre and post update:

Pre:
ProductName: Mac OS X
ProductVersion: 10.13.2
BuildVersion: 17C88
Post:
ProductName: Mac OS X
ProductVersion: 10.13.2
BuildVersion: 17C205

Since this update was just to Safari / WebKit, you would think that the kernel wouldn't need an update, which makes me wonder what else they snuck in.

Post-update here and I've still got Build 17C88. 2013 MacBook Air. Maybe your system needed a different build.
 
  • Like
Reactions: SecuritySteve
"There's also a Safari 11.0.2 update available for macOS Sierra 10.12.6 and OS X El"

At least Apple is taking care of existing users here somewhat.

When Apple says "supplemental update", does that mean there will be no "combo" version?

I guess it means just a separate update...

 
  • Like
Reactions: Pndrgnsvc
Keep believing that, if you need to.
[doublepost=1515446645][/doublepost]

Post-update here and I've still got Build 17C88. 2013 MacBook Air. Maybe your system needed a different build.
If you're still on build 17C88, the update didn't install. You should be at 17C205 after the update is installed.
 
Benchmarks are going to be completely different depending on what you do.

For most there will be almost no impact. For those that run lots of virtual machines, they will see the biggest impact.
After last macOS update (10.13.2; build 17C2205), VMware Fusion running Windows 10 x64 (4 Core, 4GB RAM) on iMac Pro 10 core; 128GB, 4TB, Radeon Pro Vega 64.

Geekbench.

Right before update
Single-core: 4915
Multi-core: 15284

Directly after update
Single-core: 5143
Multi-core: 15642

So I would not worry too much :)
Seems to me that even with the patch; it is actually faster. Reflects previous geekbench results directly on macOS as well (not only when running through VMware).
 
Last edited:
Anybody else stuck on this screen for over an hour? Not sure what I should do. Early 2013 MBP retina 13”
[doublepost=1515449942][/doublepost]Stuck
 

Attachments

  • image.jpg
    image.jpg
    517.6 KB · Views: 168
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.