Arch Linux

ExoDoom

Member

Registered: 2013-11-01

Posts: 39

Google Chrome freezing on close and using so much RAM/disk cache

Hi folks,

I'm facing some kind of weird issue with Google Chrome. Since I installed Arch on my new laptop, I noticed that sometimes the system freezes for a few seconds after closing Google Chrome. However, after I finished setting up all my system and applications and started to work with them, those few seconds turned into few minutes when closing the browser after 8 hours of work. I also noticed that, while Chrome is running, my RAM usage slowly but constantly goes up in the form of disk cache. This is conky's memgraph from the last freeze (can you guess when I closed the browser? xD)

The freeze took almost 3 minutes to complete, and this is the journalctl from the minute it happened:

sep 19 16:33:15 gram kernel: wlp0s20f3: Connection to AP (...) lost
sep 19 16:33:15 gram wpa_supplicant[695]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=(...) reason=4 locally_generated=1
sep 19 16:33:15 gram NetworkManager[475]: <info>  [1663601595.1409] device (wlp0s20f3): supplicant interface state: completed -> disconnected
sep 19 16:33:15 gram NetworkManager[475]: <info>  [1663601595.1410] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected
sep 19 16:33:15 gram NetworkManager[475]: <info>  [1663601595.2178] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
sep 19 16:33:15 gram NetworkManager[475]: <info>  [1663601595.2179] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: SME: Trying to authenticate with (...) (SSID='(...)' freq=(...))
sep 19 16:33:16 gram kernel: wlp0s20f3: authenticate with (...)
sep 19 16:33:16 gram kernel: wlp0s20f3: bad VHT capabilities, disabling VHT
sep 19 16:33:16 gram kernel: wlp0s20f3: Invalid HE elem, Disable HE
sep 19 16:33:16 gram kernel: wlp0s20f3: 80 MHz not supported, disabling VHT
sep 19 16:33:16 gram kernel: wlp0s20f3: send auth to (...) (try 1/3)
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.5590] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.5590] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: Trying to associate with (...) (SSID='(...)' freq=(...))
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.6073] device (wlp0s20f3): supplicant interface state: authenticating -> associating
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.6073] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
sep 19 16:33:16 gram kernel: wlp0s20f3: authenticated
sep 19 16:33:16 gram kernel: wlp0s20f3: associate with (...) (try 1/3)
sep 19 16:33:16 gram kernel: wlp0s20f3: RX AssocResp from (...) (capab=0x31 status=0 aid=6)
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: Associated with (...)
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
sep 19 16:33:16 gram kernel: wlp0s20f3: associated
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.6458] device (wlp0s20f3): supplicant interface state: associating -> 4way_handshake
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.6458] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> 4way_handshake
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: RSC 0000000000060000 is likely bogus, using 0
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: WPA: Key negotiation completed with (...) [PTK=CCMP GTK=TKIP]
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to (...) completed [id=0 id_str=]
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7224] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed
sep 19 16:33:16 gram wpa_supplicant[695]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=9999 txrate=1000
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7240] device (wlp0s20f3): ip:dhcp4: restarting
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7487] dhcp4 (wlp0s20f3): canceled DHCP transaction
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7487] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7487] dhcp4 (wlp0s20f3): state changed no lease
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7488] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
sep 19 16:33:16 gram NetworkManager[475]: <info>  [1663601596.7489] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed
sep 19 16:33:17 gram NetworkManager[475]: <info>  [1663601597.3914] dhcp4 (wlp0s20f3): state changed new lease, address=192.168.1.55
sep 19 16:33:17 gram dbus-daemon[467]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.4' (uid=0 pid=475 comm="/usr/bin/NetworkManager --no-daemon")
sep 19 16:33:17 gram systemd[1]: Starting Network Manager Script Dispatcher Service...
sep 19 16:33:17 gram dbus-daemon[467]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
sep 19 16:33:17 gram systemd[1]: Started Network Manager Script Dispatcher Service.
sep 19 16:33:17 gram audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 19 16:33:17 gram kernel: audit: type=1130 audit(1663601597.415:122): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 19 16:33:17 gram nm-dispatcher[551666]: req:1 'dhcp4-change' [wlp0s20f3], "/etc/NetworkManager/dispatcher.d/20-chrony": complete: failed with Script '/etc/NetworkManager/dispatcher.d/20-chrony' exited with status 1.
sep 19 16:33:17 gram NetworkManager[475]: <warn>  [1663601597.4615] dispatcher: (13) /etc/NetworkManager/dispatcher.d/20-chrony failed (failed): Script '/etc/NetworkManager/dispatcher.d/20-chrony' exited with status 1.
sep 19 16:33:27 gram systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
sep 19 16:33:27 gram audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sep 19 16:33:27 gram kernel: audit: type=1131 audit(1663601607.465:123): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Finally, this is my chrome-flags.conf:

--disable-features=UseChromeOSDirectVideoDecoder
--disable-gpu-driver-bug-workarounds
--disk-cache-dir=/run/user/1000/google-chrome-cache
--disk-cache-size=1073741824
--enable-accelerated-2d-canvas
--enable-accelerated-video-decode
--enable-features=CanvasOopRasterization,VaapiVideoDecoder,VaapiVideoEncoder
--enable-gpu-rasterization
--enable-native-gpu-memory-buffers
--enable-oop-rasterization
--enable-raw-draw
--enable-reader-mode
--enable-system-notifications
--enable-zero-copy
--ignore-gpu-blocklist
--use-gl=egl

I guess it could be because of that disk-cache-dir located in tmpfs, but the disk-cache-size theoretically limits the disk cache to 1GB, although free -hw reports >10GB of disk cache being used (and freed after Chrome is closed). I will try using a non-tmpfs location for disk-cache-dir tomorrow, but does anyone have any clue about why this could be happening? I would like to keep the browser cache on RAM for the speed and the ephemerality, but I guess it's ok to place it in the SSD if it's the root of my problem.

Thanks in advance.