I'm recently switched to using Chromium and I'm also getting weird freezes both on Chromium and Chrome.
For me journald starts going mad whenever a freeze happens.
I've submitted a bug to Chromium here: https://code.google.com/p/chromium/issues/detail?id=257998
Search Criteria
Package Details: google-chrome 132.0.6834.159-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: | 2258 |
Popularity: | 8.70 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-01-28 23:25 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- 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-full-gitAUR, pipewire-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-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)
- hub-young (optional)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 117 118 119 120 121 122 123 124 125 126 127 .. 157 Next › Last »
gadget3000 commented on 2013-07-09 14:27 (UTC)
TheWretched commented on 2013-07-08 14:48 (UTC)
I've had that sometimes (the random freezing). Moreso with chrome and it's stagnant processes than with chromium. I've had the occasional weird freeze with chromium too.
Honestly chrome / chromium has become a major pain for me with the myriad of problems it seems to have ever since KDE 4.10, mostly because it's still the only decent browser despite all these problems, meaning one has to just live with it.
<deleted-account> commented on 2013-07-08 05:08 (UTC)
Is it just me or does chrome or chromium just randomly lock up your machine for like 4 or 5 seconds randomly...... Not too sure what it maybe but it happens alot ..... It locks up only in chrome for about 5-10 seconds its very annoying ....
Det commented on 2013-07-03 22:41 (UTC)
You can just flag it.
fiveofakind commented on 2013-07-03 17:45 (UTC)
v71 md5sums:
03de683b0e9b8bf77db17060c8113d4d google-chrome-stable_current_amd64.deb
19ec74343b5396760d5d6c88d7282cfb google-chrome-stable_current_i386.deb
mike.cloaked commented on 2013-07-03 17:00 (UTC)
and hot on the heels of v70 now google-chrome-stable-28.0.1500.71-209842 is out!
Det commented on 2013-06-29 16:01 (UTC)
Added, but it'll be faster to just add that yourself.
This just moves it to /tmp anyway so it's not a real fix.
JoveYu commented on 2013-06-28 11:22 (UTC)
chrome always create "libpeerconnection.log" in my HOME
google say https://code.google.com/p/chromium/issues/detail?id=239048
maybe you can fix it for the moment
https://bbs.archlinux.org/viewtopic.php?id=163086
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.