@belochub: for the differences between those, see: https://support.google.com/chromebook/answer/1086915?hl=en
The other two are: https://aur.archlinux.org/packages/google-chrome-beta/, https://aur.archlinux.org/packages/google-chrome-dev/
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: | 2243 |
Popularity: | 7.00 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-05 19:02 (UTC) |
« First ‹ Previous 1 .. 49 50 51 52 53 54 55 56 57 58 59 .. 157 Next › Last »
@belochub: for the differences between those, see: https://support.google.com/chromebook/answer/1086915?hl=en
The other two are: https://aur.archlinux.org/packages/google-chrome-beta/, https://aur.archlinux.org/packages/google-chrome-dev/
@clepi: from my experience, it's Chrome populating its History information or something. You can see it read a lot of things from disk and load it in memory. Can be databases generated by some extensions too, mostly related to history and cache usually.
I have cleared ~/.config/google-chrome & ~/.cache/google-chrome but it still won't work.
Went through the normal troubleshooting of renaming ~/.config/xxx/ & ~/.cache/xxx/, and looking at the terminal output?
When I open chrome (or even chromium) I cannot use it - it's not responsive (can't even type anything in search bar). It've been installed without errors. Does anyone have the same issue? Moreover it works perfectly fine on my laptop, but it won't on pc.
I get the message "Chrome didn't shutdown correctly" always when I start Chrome after restarting the computer. I found out that Chrome leaves some processes running even after the browser is closed. Closing these processes with "killall chrome" before restart fixes this problem. The default signal sent by killall is "sigterm" but systemd probably sends something "faster" to the processes during shutdown, leaving them in unclean state.
Update: grepping chrome process tree root process with "pgrep -o chrome" and then killing that process + waiting for the directory to disappear from proc works better than "killall" that sometimes works, sometimes doesn't.
zerophase: "Is anyone else having issues with Chrome refusing to launch lately?". Yes. I just moved from chromium to chrome in one system with Cinnamon and other with Gnome 3. Launching chrome in Cinnamon doesn't work (hangs forever) but in Gnome 3 it does so there does seem to be that almost required dependency to gnome-keyring.
Is anyone else having issues with Chrome refusing to launch lately?
Just getting this error:
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
EDIT: Well, I just had to install gnome-keyring. Have no idea what changed requiring that for Chrome to run.
I also see severe memory usage issue in recent versions. I open hundreds of tabs and use tab suspender. It used to work with only less than 2GB, now I have to restart it once every day to free 6GB of memory or it will take all of swap.
I see. Didn't realize about the previous high memory comment. I guess it is probably the same thing. I don't know, since I was not monitoring memory usage and the computer became truly unusable even after waiting for a few minutes, so I couldn't even change to a terminal. I will check today and see if the memory is also the issue in my case.
After doing some tests, my issue seems different. Memory usage was a total of about 1.7GB (in a system with 8GB) with 8 tabs open. I tried to resize the Chrome window and suddenly the whole thing froze....
As in like as per the previous comments?
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.