I've noticed with more frequency that after waking from sleep, Chrome or some of its tabs will crash. It can happen immediately or shortly after. A kernel crash or system freeze happens less frequently but is more disruptive when they happen.
This is happening on my main system that has 3 monitors (2 are 120Hz), an AMD CPU with integrated graphics and a discrete Nvidia GPU. The monitors are connected to the motherboard (1 HDMI and 2 DisplayPort that are daisy-chained) rather than to the discrete graphics so I can preserve as much VRAM for LLM inference.
Initially, I though the culprit was the Nvidia driver since the most common responses on the Internet mention them. The next most common response was to turn off hardware acceleration in Chrome.
chrome://gpu revealed that the iGPU was only being allocated 512MB of memory which not enough with a multi-monitor setup. This was being automatically set in the BIOS so I changed the UMA Frame Buffer Size (Found under NB Configuration) to 1GB.
Next, Chrome showed it knew there are two graphics option so this tells it to almost use the integrated graphics.
google-chrome-stable --disable-gpu-driver-bug-workarounds --gpu-testing-vendor-id=<vendor id> --gpu-testing-device-id=<device id>There are some settings for the Nvidia card that might also improve stability. Edit /etc/modprobe.d/nvidia.conf and add the following settings might improve stability but might also slow waking up:
options nvidia "NVreg_PreserveVideoMemoryAllocations=1"
options nvidia "NVreg_TemporaryFilePath=/var/tmp"
options nvidia "NVreg_EnableS0ixPowerManagement=1"
options nvidia "NVreg_PreserveVideoMemoryAllocations=1"To make sure the system leverage these values:
sudo dracut -f
sudo rebootTip: Restart the Cinnamon process without losing your open windows by pressing Alt + F2, typing r, and hitting Enter
No comments:
Post a Comment