When using Chrome, why is google maps so slow on my 2014 15" Macbook pro? IG version, not the one with the dedicated video card.

[jackson6]

I am running MacOS 15.3 via OCLP. When I used firefox on the same laptop with google maps, it was at the normal speed. So this doesnt make sense to me, is it Chrome's fault that google maps is slower than firefox when visiting the exact same website?

does anyone else have this problem?

 

[AlixSPQR]

I have a MBP 15" 2014 with dedicated GPU, and I find that model too old for macOS 15, so I reverted to macOS 14. Especially graphics performance is much worse in macOS 15. The TV app doesn't work, for instance. I suppose this also hits hard in Chrome's case. You can ask in OCLP's Discord about it.

 

[jackson6]

I can understand that the hardware is too old, but it doens't make sense because google maps is fast on Firefox, but slow on Chrome (and I would much rather use Chrome).

 

[dmccloud]

Based on your posts, the issue is likely with Chrome itself. It's hard to say why you are experiencing the issue given that you're running an OS that is not officially supported on your hardware and there is no mention of which version of Chrome you are running. If it was a hardware and/or OS related issue, then the performance should be equally sluggish across all browsers. Have you tested the performance in Safari?

 

[jackson6]

Based on your posts, the issue is likely with Chrome itself. It's hard to say why you are experiencing the issue given that you're running an OS that is not officially supported on your hardware and there is no mention of which version of Chrome you are running. If it was a hardware and/or OS related issue, then the performance should be equally sluggish across all browsers. Have you tested the performance in Safari?

I did a search for hardware acceleration (in the Chrome settings) and turned it off, restarted the browser, and turned in back on.

I just tested it and I think that might have partly fixed it (it is laggy when i first visit the google maps site, but after the first search it is a bit smoother, not quite fast enough, but at this point I will live with it unless some has more ideas on how to improve this).

Posting this in case others run into the same problem.

Does anyone who has technical knowledge (or not) know why the turning off and on again helped fix the problem?