Package Details: google-chrome 129.0.6668.58-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: 2236
Popularity: 7.19
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (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 .. 123 124 125 126 127 128 129 130 131 132 133 .. 157 Next › Last »

<deleted-account> commented on 2013-04-11 15:17 (UTC)

You'll get the tray icon by checking "Continue running background apps when Google Chrome is closed" in the settings. I'm not sure, but when this is enabled chrome won't leak processes any more. Each time chrome is restarted the number of processes is not higher as the last time. Which is the case when this option is not set. Each time more and more processes are added. Unfortunately selecting "exit" on the tray icon does *not* stop the processes. Still needed to do killall chrome. :-/

TheWretched commented on 2013-04-11 15:14 (UTC)

Going to give chromium another go. When I first upgraded to 4.10 I was having problems with it too. I don't think this is related to the stale processes but I have another major annoyance in chrome that I was also getting in chromium with 4.10. That is when I middle click a link to open in a new tab it will frequently freeze the browser and result in a tab that looks like about a quarter the size it should be. Again resulting in a pkill being needed. This persists even with the latest KDE and the latest chrome as of this writing. I guess well see if this is still the case with chromium.

Det commented on 2013-04-11 12:49 (UTC)

They like your memory. They don't wanna go. You should be flattered.

<deleted-account> commented on 2013-04-11 07:46 (UTC)

Processes are stuck in memory again. Damn...

Det commented on 2013-04-09 18:40 (UTC)

I don't.

MrTux commented on 2013-04-09 18:10 (UTC)

source=("https://dl.google.com/linux/direct/google-chrome-${_channel}_current_${_arch}.rpm") I think use this is better for update

<deleted-account> commented on 2013-04-08 21:47 (UTC)

FYI: If you are having problems with zombie processes (Chrome_ProcessL, etc.) and you are using the nvidia blob driver, the problem is known to upstream (http://crbug.com/177218) and is in fact due chrome's tcmalloc clashing with a bug in the nvidia driver. The only "workaround" is to use chromium from [extra], AFAIK, since it disables tcmalloc at compile time.

Det commented on 2013-04-04 10:55 (UTC)

Let's hope 4.10.2 makes things work again. Seems like the whole 4.10 series was a bit half-assed anyway: https://bugs.kde.org/show_bug.cgi?id=316086

<deleted-account> commented on 2013-04-04 06:48 (UTC)

Yesterday I had a Chrome tray icon - with which you can tell the thing *not* to remain in background when closed. This actually works for me ! :-) So they have been messing with processes...

heaven commented on 2013-04-03 19:45 (UTC)

Also have all those problems with sound and leftover processes.

« First ‹ Previous 1 .. 123 124 125 126 127 128 129 130 131 132 133 .. 157 Next › Last »