Issue metadata
Sign in to add a comment
|
Frequent brief lockups of both browser and renderer processes |
||||||||||||||||||||
Issue descriptionVersion: 54.0.2824.0 (Official Build) dev (64-bit) - Linux Version: 54.0.2830.1 (Official Build) canary SyzyASan (32-bit) - Windows Updated Chrome to the above versions yesterday. Today, both the browser process and individual renderers on both machines are locking up for 10-20 seconds at a time, randomly. (1) On the Linux machine the first lockup was immediately on the first run after a reboot, for about 10 seconds. The first thing I did was remove an extension that was hidden in the hamburger menu, by opening the hamburger menu and right-clicking on it and hitting "Remove". The browser process locked up for over a minute after the menu closed, before the "Are you sure?" dialog opened. (2) Since then, individual tabs have frozen, usually while scrolling with the mouse wheel, at random times but never for as long. Also when this happens, I tend to try to open a new tab with the tab bar button, and often (but not always) find that the browser process is frozen too. I haven't noticed if the browser process freezes while no tabs are frozen. The Windows machine shows behaviour (2) as well, and it started a few minutes before I rebooted the Linux machine. Both machines are syncing the same profile. Possibly unrelated: on the Windows machine, a Google-internal extension started crashing every few minutes this morning as well. (It's since backed off to crashing only occasionally - before today it was rock-solid.) The same extension hasn't had any problems on the Linux machine.
,
Aug 18 2016
This is still happening after I roll back to M52, so it's almost certainly something in my user profile. Trying with a blank profile now.
,
Aug 22 2016
,
Aug 30 2016
No longer happening with 55.0.2844.1 (Official Build) canary SyzyASan (32-bit) Will wait until I can confirm it's gone on Linux too before I close this.
,
Dec 19 2016
--Chrome Identity automated triaging-- This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 28 2017
,
Oct 9 2017
I don't know if this bug from exactly a year ago is still considered open, but I started seeing this behavior within the last two weeks. This is on Linux, Version 62.0.3202.45 (Official Build) beta (64-bit) Since it seems like this bug is accepted, I figured I'd try to bump it rather than opening a new one.
,
Oct 8
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 8
Is this bug still valid? |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by joenotcharles@chromium.org
, Aug 17 2016