New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 903944 link

Starred by 2 users
Status: Archived
Owner: ----
Closed: Jan 17
Cc:
█ jayhlee@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Chrome-Bug-Cleanup


Sign in to add a comment

Expired session Gsuite reauth prompt has high CPU usage

Project Member Reported by vkhabarov@chromium.org, Nov 9 
Chrome version: found in v66+
OS version: Linux, Windows
Case#: 17243398

Description:
Customer sets Web session duration to some setting other than "Session never expires", for example 4hr. Then this timeout passes, he opens tab with reauth prompt and notices significant increase in CPU load.
We reproduced this issue with v66+ (oldest we tried)

Steps to reproduce: 
1. Set up Web session duration in Security in Admin Console
2. Login to browser, open Google services tabes (eg, gmail and Drive), switch to other tab.
3. Wait for timeout to pass
4. Open tab with "To continue, verify it's you" prompt
5. Open Chrome Task Manager to observe CPU usage


Current Behavior / Reproduction: 
Tab shows high (17-40) CPU usage

Expected Behavior: 
Tab shows low CPU usage like normal login prompt

Drive link to logs: 
Screenshots - 
https://drive.google.com/open?id=1jmHy5njVLS0QOyocG5z_q1NCzh85LOvO
(taken from Chromium, but Chrome behaves the same)

Comment 1 by sylcat@google.com, Jan 11 

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time.
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Thursday, 01/17/19 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Comment 2 by sylcat@google.com, Jan 17 (5 days ago)

Status: Archived (was: Untriaged)
Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.
►

Sign in to add a comment