Google Chrome Not Running Off Of eGPU After 10.14.6 Supplemental Update
 
Notifications
Clear all

Google Chrome Not Running Off Of eGPU After 10.14.6 Supplemental Update  

  RSS

Thomas Liviakis
(@thomas_liviakis)
Active Member
Joined: 1 year ago
 

I used to be able to run Google Chrome on my Sapphire Pulse Radeon RX 580 eGPU before the latest 10.14.6 Supplemental Update. When I installed this update yesterday, Google Chrome refuses to run off of the eGPU and instead runs off of my Nvidia Geforce GT 650M dGPU. Firefox, however, still runs off of my eGPU like normal. I checked to make sure that the "Prefer External GPU" option was checked for Google Chrome and it is. I tried uninstalling and reinstalling the purge-wrangler.sh and set-eGPU.sh and nothing changed. I also tried reinstalling Google Chrome–still no change. This doesn't seem to be happening to the other applications. Just to Google Chrome.

Does anyone know what the problem could possibly be? I would appreciate any kind of help.

I have a 15 inch mid 2012 Macbook Pro Non-retina GT650M laptop with a Razer Core X Chroma enclosure and a Sapphire Pulse Radeon RX 580 8G eGPU.

Thomas Liviakis

Computer: Macbook Pro Mid 2012 Non-Retina GT650M with Intel HD 4000 iGPU
Enclosure: Razer Core X Chroma
eGPU: Sapphire Pulse Radeon RX 580 8G


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
 

https://egpu.io/forums/pro-applications/chrome-browser-not-using-egpu/

There are probably more discussions floating around - I suggest searching the forums.

 

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Thomas Liviakis
(@thomas_liviakis)
Active Member
Joined: 1 year ago
 

Thank you for your reply. I looked at https://egpu.io/forums/pro-applications/chrome-browser-not-using-egpu/ and tried this command in the terminal as instructed, "$ chromium --gpu-active-vendor-id=0x8086 --gpu-active-device-id=0x0166", but I got "-bash: $: command not found". I tried adding the command line flags "--foo --bar=2" to it, but nothing executed. Here's the readout of chrome's GPU use from "chrome://gpu": (I'm not sure how to paste an image here so sorry if it's small)

image

 How do I enter this command in Terminal?

Thomas Liviakis

Computer: Macbook Pro Mid 2012 Non-Retina GT650M with Intel HD 4000 iGPU
Enclosure: Razer Core X Chroma
eGPU: Sapphire Pulse Radeon RX 580 8G


ReplyQuote
clarketus
(@clarketus)
Eminent Member
Joined: 3 years ago
 

I have the same laptop as you, and I posted in this thread a while ago when someone else had issues with Chrome using the eGPU. Perhaps this could be of use for you:

https://egpu.io/forums/mac-setup/strange-lag-performance-issue-on-egpu-chrome/

 

Admittedly, I never actually got Chrome to use the eGPU at all without what I mentioned in that thread, so I am curious how it was working for you before your recent update.

Guides:
Mid 2012 15" MBP GT650M Non Retina + RX580@10Gbps-TB1 (Gigabyte Gaming Box via TB3->TB2 adapter) + macOS 10.13.4 / Win10

 
2012 15" MacBook Pro (GT650M) [3rd,4C,Q] + RX 580 @ 10Gbps-TB1>TB3 (Gigabyte Gaming Box) + macOS 10.13 & Win10 [build link]  


ReplyQuote
Thomas Liviakis
(@thomas_liviakis)
Active Member
Joined: 1 year ago
 

@clarketus, Thanks for the reply. I saw your post earlier today when @mac_editor told me to look at other people's posts on the egpu.io site. However, I would prefer not to use an external monitor when using Google Chrome. My laptop's internal monitor works wonderfully with applications like Firefox and Final Cut Pro. I just don't understand why Chrome stopped working right after the 10.14.6 supplemental update, which was released 3 days ago. I read on a forum that Chrome has a bug preventing Nvidia eGPUs from being used, but I have an AMD eGPU. Thank you for sending me the link to your post though.

Earlier today, I replied to @mac_editor with a post asking if he knew how to enter in this terminal command: $ chromium --gpu-active-vendor-id=0x8086 --gpu-active-device-id=0x0166. Someone on egpu.io was able to make Google Chrome boot from their eGPU always with this terminal command. I kept getting an error saying -bash: $: command not found. Do you happen to know how I can successfully execute this code or access Chrome's GPU configuration page like I can in Firefox?

Again, thanks for the help. I appreciate it.

 

Thomas Liviakis

Computer: Macbook Pro Mid 2012 Non-Retina GT650M with Intel HD 4000 iGPU
Enclosure: Razer Core X Chroma
eGPU: Sapphire Pulse Radeon RX 580 8G


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
 

@thomas_liviakis, it should be in the thread I linked to you - I think you have to use the correct application path. I don’t use Chrome so I don’t have insight myself. 

 

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
Thomas Liviakis
(@thomas_liviakis)
Active Member
Joined: 1 year ago
 

@mac_editor, I read the thread that you linked to me and used the application path that it provided me: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome. When I paste it in terminal, it either opens up Chrome and freezes the terminal window or when I use the "cd" command to see if the path exists, it says "Not a directory". I'm very new at terminal and don't know how to use it very well, so I was wondering if you know of any commands I can try to specify the correct directory.

Also, here's what it displays when I paste the application path from the thread you posted:

2020-10-05 21:40:32.995 Google Chrome Helper (GPU)[5414:79821] apply_selection_policy_once: prefer use of removable GPUs (via com.google.Chrome.helper:GPUSelectionPolicy->preferRemovable)
2020-10-05 21:40:33.193 Google Chrome[5396:79706] apply_selection_policy_once: prefer use of removable GPUs (via com.google.Chrome:GPUSelectionPolicy->preferRemovable)

It then just freezes after this.

This post was modified 12 months ago

Thomas Liviakis

Computer: Macbook Pro Mid 2012 Non-Retina GT650M with Intel HD 4000 iGPU
Enclosure: Razer Core X Chroma
eGPU: Sapphire Pulse Radeon RX 580 8G


ReplyQuote
wired
(@wired)
Active Member
Joined: 3 months ago
 

Has anybody gotten this to work?

Absolutely infuriating problem. I have a eGPU setup, now with with Kryptonite (previously purge-wrangler) that works with other applications like the Heaven Benchmark, but not Chrome. I had it working previously like the OP, but it broke after the update, and I gave up getting it to work at that time, now trying to pick up the mantle again because I need the performance.

I've tried:

- right clicking the app and selecting "prefer external grahics card"

- selecting "prefer external graphics card" on the Google Helper process (and other processes) inside the package,

- setting flags, Based on other threads, I've tried both:

  • /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --gpu-active-vendor-id=0x8086 --gpu-active-device-id=0x67df

and

  • /Applications/Google Chrome.app/Contents/MacOS/Google\ Chrome --flag-switches-begin --flag-switches-end --gpu-testing-vendor-id=0x1002 --gpu-testing-device-id=0x67df

But Chrome still persists using the damn integrated 650M dGPU nonetheless. Considering a switch to Windows over this f*****g crap; it's so sloppy, unnecessary and typical of Apple.

And for those who suggest switching browser, sadly I'm relying on a Chrome-exclusive plugin, or I'd be over the hills and far away already, trust me...

Macbook 2012 2,3ghz 16gb, RX570 eGFX Sonnet Egpu Puck, MacOs Mojave 10.14.16


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 5 years ago
 
Posted by: @wired

Considering a switch to Windows over this f*****g crap; it's so sloppy, unnecessary and typical of Apple.

This has nothing to do with Apple actually, it’s just Chrome being Chrome on macOS. Have you tried the headless monitor trick mentioned in one of the linked threads above? Maybe you can use your extension on Chromium (or other Chromium-based browser) instead and try to see if you can get that to work (maybe others have more config options) with eGPU? I don’t know much about Chrome stuff so grasping at straws.

"Desultory reading is delightful, but to be beneficial, our reading must be carefully directed." — Seneca

Author: kryptonitepurge-wranglertbt-flashpurge-nvdaset-eGPU
Insights Into macOS Video Editing Performance

Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro

 
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]  


ReplyQuote
wired
(@wired)
Active Member
Joined: 3 months ago
 
Posted by: @mac_editor
Posted by: @wired

Considering a switch to Windows over this f*****g crap; it's so sloppy, unnecessary and typical of Apple.

This has nothing to do with Apple actually, it’s just Chrome being Chrome on macOS. Have you tried the headless monitor trick mentioned in one of the linked threads above? Maybe you can use your extension on Chromium (or other Chromium-based browser) instead and try to see if you can get that to work (maybe others have more config options) with eGPU? I don’t know much about Chrome stuff so grasping at straws.

I appreciate you effort. However, I am running on an external monitor cloning the internal screen, and have also tried clamshell mode to no avail, so the HDMI-headless is not a solution. The plugin does not work on other Chromium based browsers, probably because of the fact that Google Chrome is a POS too.

But the fact that it broke after a "supplemental" MacOS update does point to the fact that Apple is at fault here, and let's be honest, it's rather typical, which is why we have to mess with getting proper EGPU and hack the OS to support it - because the Nvidia drivers sucks and the TB1 Macbooks lacks MST support in MacOS even though this works in fucking Windows - in the first place.

It is typical Apple all the way, and has Apple in neon-glowing spraypaint written all over it; I'm getting rather sick of it, and they would be wise to drop the arrogant act now that Windows is catching up to MacOS as far as innovation, or at least commoditisation! And as far as their image of a politically correct company virtue signalling over being "green" and the rest of it; just fuck off already!!!!

Macbook 2012 2,3ghz 16gb, RX570 eGFX Sonnet Egpu Puck, MacOs Mojave 10.14.16


ReplyQuote