zlacker

[parent] [thread] 4 comments
1. steveB+(OP)[view] [source] 2023-07-18 12:53:45
I found chrome on macOS to be a sloppy implementation

Years ago I remember it was the one app that could reliably kernel panic my MacBook

Strange stuff

replies(1): >>itsTyr+55
2. itsTyr+55[view] [source] 2023-07-18 13:20:00
>>steveB+(OP)
how the shit does a browser just casually kernel panic the OS ‽ O_o
replies(2): >>yjftsj+v6 >>steveB+rg
◧◩
3. yjftsj+v6[view] [source] [discussion] 2023-07-18 13:26:41
>>itsTyr+55
Blind guess: GPU driver bug
replies(1): >>steveB+Ee
◧◩◪
4. steveB+Ee[view] [source] [discussion] 2023-07-18 13:56:17
>>yjftsj+v6
as I recall, yes this was it
◧◩
5. steveB+rg[view] [source] [discussion] 2023-07-18 14:02:32
>>itsTyr+55
It was literally the only app that kernel panic'd any of my Macs in years, and it did it repeatedly on a few bad releases across a number of years.

Given the number of devs at GOOG that presumably used Macs, it was astonishing sloppiness to have been let out the door

2012 there was ultimately an Apple driver issue, but only seemed GOOG was impacted / let the code out the door / couldn't be bothered to patch around in meantime https://www.cnet.com/tech/computing/google-yes-chrome-is-cra...

This was not the first or last Chrome MacOS kernel panic. Personally I recall them happening post 2017 as they were happening when I lived in an apartment I moved into around then. Searching around I see references to more of these types of incidents in later years like 2016 & 2019.

[go to top]