Hello, I'm experiencing a problem with Chrome: while uploading a fair amount of photos on Google Photos (over 1000 photos) or videos (45 videos), after two or three files processed Google Chrome gets stuck and the popup "Page unrensposive" comes out and I need to kill chrome.
I tried with Chromium on the official repositories and I have no problem with it.
Any idea why? Do you have any suggestion on how to debug this?
Search Criteria
Package Details: google-chrome 129.0.6668.58-1
Package Actions
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: | 2237 |
Popularity: | 8.05 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-09-17 21:41 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libcups (libcups-gssapiAUR, libcups-gitAUR, cups-gitAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (41)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-bypass-paywalls (optional)
- chromium-extension-adnauseam (optional)
- chromium-extension-autoscroll (optional)
- chromium-extension-plasma-integration (optional)
- chromium-extension-runet-censorship-bypass (optional)
- chromium-material-icons-for-github-bin (optional)
- chromium-vencord (optional)
- chromium-vencord-bin (optional)
- chromium-vencord-git (optional)
- dedao-dl-bin (optional)
- endpoint-verification-chrome
- endpoint-verification-minimal
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- hub-kids (optional)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 56 57 58 59 60 61 62 63 64 65 66 .. 157 Next › Last »
TiD91 commented on 2017-06-16 20:36 (UTC)
valandil commented on 2017-06-10 18:27 (UTC)
@Det I do, but after resigning it I had lost my Session Manager info.
I'll try with google-chrome-beta to see if it repopulates that info.
Det commented on 2017-06-10 08:00 (UTC)
@valandil, don't you sync your profiles with your Google account?
manjabuntu.com commented on 2017-06-10 05:43 (UTC)
At the first start it is absolutely always chrome crashes, absolutely always. Such problems began with this version
valandil commented on 2017-06-10 01:03 (UTC)
@Det: Indeed, this works. I'll try to seek some help in the Chrome help forums, as I'd rather not lose my profile info.
Thanks!
Det commented on 2017-06-09 19:07 (UTC)
Can't say. Someone in there also had an i7-3770. If Beta Channel works (60.x), then maybe you just need to stick to that branch, until Stable syncs up.
Beta Channel also has its own settings dir, so maybe try a clean new profile by renaming ~/.config/google-chrome/ and ~/.cache/google-chrome/?
valandil commented on 2017-06-09 18:12 (UTC)
Have you ever seen this error?
https://pastebin.com/9a9DBrtP
I've come accross this in old bugs (https://bugs.chromium.org/p/chromium/issues/detail?id=544160), but I think they all pointed to the use of old processors that didn't support SSE2. I'm on an Intel Core i7 which definitely supports SSE2, and still have this mistake.
google-chrome-beta starts up just fine.
Det commented on 2017-06-06 14:21 (UTC)
Yeah the Beta and Dev's are too, just didn't notice the bump to 59:
- https://aur.archlinux.org/packages/google-chrome-beta/
- https://aur.archlinux.org/packages/google-chrome-dev/
lonaowna commented on 2017-06-06 07:47 (UTC)
sflor is right. see also: https://bugs.archlinux.org/task/47682
sflor commented on 2017-06-06 07:36 (UTC)
Dependency change? gtk2 -> gtk3
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.