Friendly correction: The 2011 Macbook Pro was AMD chip not NVIDIA. My 2008 Macbook Pro was NVIDIA.
>No, Chrome didnt kill your Macbook,
Yes, I totally understand that perspective and it's more Macbook's hardware defect rather than Chrome programmers. Intellectually, I do get that. I'm just saying that the previous 8 years of running things like MS Excel, MS Outlook, Photoshop, etc didn't peg the cpu at 100% and kill the (defective) Macbook. It was Chrome and its "helpful antivirus software" that I never asked for that finally stressed out the machine. I made a conscious decision to use Chrome the browser but that doesn't mean I wanted to run a hidden software scanning tool.
The Macbook failure is what made me aware of Chrome's new hidden scanner and thus, I disabled it on all non-Apple computers such as Lenovo ThinkPad and my ASUS motherboard desktops. I really don't need Chrome's scanner.
Friendly correction: The 2011 Macbook Pro was AMD chip not NVIDIA. My 2008 Macbook Pro was NVIDIA.
>No, Chrome didnt kill your Macbook,
Yes, I totally understand that perspective and it's more Macbook's hardware defect rather than Chrome programmers. Intellectually, I do get that. I'm just saying that the previous 8 years of running things like MS Excel, MS Outlook, Photoshop, etc didn't peg the cpu at 100% and kill the (defective) Macbook. It was Chrome and its "helpful antivirus software" that I never asked for that finally stressed out the machine. I made a conscious decision to use Chrome the browser but that doesn't mean I wanted to run a hidden software scanning tool.
The Macbook failure is what made me aware of Chrome's new hidden scanner and thus, I disabled it on all non-Apple computers such as Lenovo ThinkPad and my ASUS motherboard desktops. I really don't need Chrome's scanner.