Mercury
Mercury copied to clipboard
GPU process always using 100% CPU on latest NVIDIA drivers on Windows 11 (Mercury 121.0.2)
For some bizarre reason, the latest NVIDIA 551.23 driver under Windows 11 seems to cause Mercury 121.0.2's GPU process to use 100% of the CPU, even while idling.
Disabling hardware acceleration does fix the issue.
I tried profiling it and this is what I get:
EDIT:
Stock Firefox 122.0 does not seem to have this issue.
I also tried disabling all the add-ons on Mercury, but that did not fix the issue.
also facing the similar issue
@KaleidonKep99 @5aad666 It may be related to pref("layers.acceleration.force-enabled", true);
Open about:config
and set layers.acceleration.force-enabled
to "false" and see if it fixes your issue.
If not, ver 122 releases are coming soon and we can retest.
Also experiencing this, NVIDIA 551.23 on Win10.
layers.acceleration.force-enabled=false and disabling hardware acceleration in the settings (just one of those two did not work. had to use them together) "fixed" (i like hwaccel :c) this issue for me.
still an issue with 122 for me
Testing on 122.0.2 and the issue persists for me too!
I started to get this issue after updating to 123.0.1 version. Using Nvidia (1660ti) and the latest drivers. Let me know if I can provide some data that you need.
I'm building 123.0.2 and I'm seeing the same thing.
Property | Value |
---|---|
OS Name | Microsoft Windows 11 Home |
Version | 10.0.22621 Build 22621 |
Other OS Description | Not Available |
OS Manufacturer | Microsoft Corporation |
System Name | SURFACEBOOK3 |
System Manufacturer | Microsoft Corporation |
System Model | Surface Book 3 |
System Type | x64-based PC |
System SKU | Surface_Book_3_1899 |
Processor | Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz, 1498 Mhz, 4 Core(s), 8 Logical Processor(s) |
BIOS Version/Date | Microsoft Corporation 19.100.140, 12/8/2023 |
GPU NVIDIA | GeForce GTX 1660 TI |
GPU Driver | 551.76 |
Seeing the same thing on an AMD system, though I never actually noticed it until I was on a machine with fewer cores.
Adding mercury.exe with absolute path to the Mozilla Firefox Nvidia profile with nvidia Profile Inspector seems to have fixed this issue for me.
Easiest and least invasive solution is to change the executable name in Program Files\Mercury from mercury.exe to firefox.exe and once again set browser as default / modify associations. This issue stems, as @reck0 pointed out, from NVIDIA profiles. It does appear that NVIDIA has a profile for Gotham Knights game, where one of the binaries is mercury.exe so when the browser is running the driver thinks there is Gotham Knights game running and it uses that profile. So to sum up, you can modify the executable name, add mercury.exe to Mozilla Firefox profile or remove mercure.exe from Gotham Knights profile. If you decide to go with the profile inspector route be sure to remember not to do clean driver install when updating or you will need to modify the profile again. It would be super nice if the developer could implement some routine in the installer to change the executable name on systems with an NVIDIA GPU or prompt when starting the browser on such system to guide users on what to do as I suppose that NVIDIA will not be very willing to modify their game profile on account of the Mercury browser.
@inteliboy I don't have any profiles for Firefox set up in Nvidia. Is this something that Nvidia sets up in the background? I can't find it in either the Nvidia Experience app or in the Nvidia Control Panel.
Drivers have a lot of built-in profiles. They do show up in NVIDIA Control Panel if you have them installed and at least once ran them (name of the executable is important). You can see them all by using NVIDIA Profile Inspector and only there can you perform the mentioned modifications. https://github.com/Orbmu2k/nvidiaProfileInspector/releases
niedz., 14 kwi 2024, 13:28 użytkownik Jordan Wages @.***> napisał:
@inteliboy https://github.com/inteliboy I don't have any profiles for Firefox set up in Nvidia. Is this something that Nvidia sets up in the background? I can't find it in either the Nvidia Experience app or in the Nvidia Control Panel.
— Reply to this email directly, view it on GitHub https://github.com/Alex313031/Mercury/issues/116#issuecomment-2054017014, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA32BKWMKWATIFBYQOQTRDY5JR4ZAVCNFSM6AAAAABCO2K7O2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGAYTOMBRGQ . You are receiving this because you were mentioned.Message ID: @.***>