Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Has your 2018 Macbook Pro KP'd with the Bridge OS error since 10.14.3 GM


  • Total voters
    107
  • Poll closed .
Return it and get the same config if you wanna stay on macOS.
I did return it, yesterday. To Apple's credit, they did not give me a hassle, but there was no attempt to understand the issue or offer a path forward. Originally I was going to just wait 3 months and try again. Problem is, I did get to experience what 18-cores could do for my workflow. Grin.

So, I gave the entire experience some thought overnight. After exclusively buying Apple hardware for 15 years, I decided it was time to give PCs a try. I ordered a similarly configured PC tower this morning. From a productivity perspective, there's nothing I'm using that is MacOS exclusive. Even if the PC gives me trouble, at least I can swap out hardware pieces and move forward. In the case of the iMac Pro, I either hoped my render would finish or... well, no, I only had one option.

I'm not a fan of Windows, but I need to keep making a living. I can't let a chip that adds almost no value to an $11,500 machine be the reason I miss deadlines.
 
Personally, I think the T2 is just a crappy chip that just happens to misbehave on limited scope and set of circumstances that doesn't rise to the level of a priority problem at Apple. Well that, and people who don't have issues with it tend to call us crazy. I agree with CMiYC's ultimate conclusion above. However, I'm too late to return mine and start messing about, so I just live with it, which generally happens rarely now and only on startup, so it doens't affect my workflow much.
 
Personally, I think the T2 is just a crappy chip that just happens to misbehave on limited scope and set of circumstances that doesn't rise to the level of a priority problem at Apple. Well that, and people who don't have issues with it tend to call us crazy. I agree with CMiYC's ultimate conclusion above. However, I'm too late to return mine and start messing about, so I just live with it, which generally happens rarely now and only on startup, so it doens't affect my workflow much.
That seems right. But I think it will be fixed. Just slowly.
 
That seems right. But I think it will be fixed. Just slowly.

I also think a firmware update will eventually fix it. Had my first ”Bridge OS 3.3” crash the other day and I've have been using the computer at least every weekday for a couple of months now. Might be difficult to track down the problem, but keep sending the logs to Apple I guess...
 
I personally don't think it will be fixed in software. I think that if it could it would have been fixed long ago. It will take a new rev of hardware and more importantly, Apple to take it seriously as a problem, which I happen to think they don't. Yeah I know that sounds pessimistic, but I call it as I see it.

anyway, still seems like problem in this thread:

https://forums.macrumors.com/thread...rashing-with-bridge-os-error.2128976/page-131

Lucky the new imac still has no T2.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.