Package Details: google-chrome 133.0.6943.126-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2261
Popularity: 8.10
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-02-19 09:28 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 157 Next › Last »

ftwcpc commented on 2023-08-15 02:33 (UTC) (edited on 2023-08-15 02:47 (UTC) by ftwcpc)

Once live captions is enabled, chrome tab CPU usage exceeds 500%, has anyone experienced this issue?

fixed after clear cache data and relaunch the chrome

dsyzling commented on 2023-08-12 16:07 (UTC)

@minime I think I managed to clear my issue by resetting chrome settings (Settings-Reset Settings) - no idea if this will cure your issue but it might be worth testing. But after the reset Chrome is no longer leaving a process in the background at 100%.

minime commented on 2023-08-12 13:28 (UTC)

@dsyzling Just so you know, I think I have the same issue. Sometimes CPU utilization spikes up until chrome process gets killed. I wasn't able to pinpoint the exact scenario for a repro, it happens during google meet calls, during playing YT vids, sometimes even in idle. I run the latest arch kernels, proprietary nvidia drivers, i3wm. Machine is a PC, intel 6700k, 16gb ram. Hardware acceleration is on.

dsyzling commented on 2023-07-19 13:56 (UTC)

Has anyone else experienced 100% CPU utilisation with Chrome - even after closing the browser window I'm left with a chrome process at 100%? This started to occur with a new release a few months back. I've tried hardware acceleration flags and as far as I can see I have hardware decoding enabled. Machine is a Carbon X1 (gen 6). I can watch youtube videos without any issues but if I trigger a google search which yields youtube videos the cpu on one process goes to 100% and I have to manually kill the process from the command line.

georgewoodall82 commented on 2023-07-09 14:34 (UTC)

I think trusted should be removed from the description

joaobrlt commented on 2023-06-26 19:45 (UTC) (edited on 2023-06-26 19:45 (UTC) by joaobrlt)

Can confirm the behavior described by dr1fter. Since the last update, google-chrome is unresponsive after resuming from standby.

Existing web pages are displayed properly but the GUI is completely unresponsive (change tab, add a tab, etc.).

I use Manjaro, linux-61 (6.1.31-2), gnome-shell (1:44.1-3) and linux61-nvidia (530.41.03-13).

I will try to find the logs next time it happens.

vikrend commented on 2023-06-08 17:50 (UTC)

Dark mode is not working in last update

ollosh commented on 2023-06-08 17:01 (UTC)

Did anything happen recently with forcing dark theme in chrome? Every time I start chrome now all of the pages are dark when following system theme. I do have a light/dark theme switcher script for my setup, but when I check the flags with chrom://version they are correctly passed. Any ideas?

dr1fter commented on 2023-06-08 06:02 (UTC)

Since recently (I do not track google-chrome versions), google-chrome will be frozen for ~1m after resuming from standby (systemctl suspend). I saw this behaviour for many months (started about one year ago); then about two months ago, the bug was gone (now it's there again).

The displayed webcontents are shown w/o any errors, however the GUI is fully unresponsive. If e.g. opening a new tab, this will happen after the application "thaws" after the mentioned ca. 1m. As a workaround, I tend to killall chrome (aka restart).

I run full system updates (pacman -Syu) daily, and update my AUR-packages about once a week. I use an NVIDIA graphics card w/ the non-free nvidia package.

xxxxp commented on 2023-06-06 03:17 (UTC)

hardware acceleration works again, thanks

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 157 Next › Last »