New issue
Advanced search Search tips

Issue 899556 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 867970



Sign in to add a comment

Chrome crashed while locking screen

Project Member Reported by bcornell@google.com, Oct 28

Issue description

Chrome Version       : 69.0.3497.95
OS Version: 10895.56.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. ?
2. Open lid

What is the expected result?

Computer is locked, asks for password, shows previously open tabs when password entered.


What happens instead of that?

Screen was not locked, restore tabs button visible.


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 10895.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.95 Safari/537.36


I put my computer to sleep by closing the lid and putting it in my bag on Friday afternoon. This afternoon I opened it up to check something and it immediately showed me the restore pages button with no login. Clicking the restore button reopened all of my tabs logged into my corp account with confidential information.

I see no crashes in chrome://crashes with relevant timestamps.

I have not been able to reproduce this.
 
Owner: r...@chromium.org
Status: Assigned (was: Unconfirmed)
rkc@, do we know of any other reports?
Cc: kerrnel@chromium.org
Blockedon: 867970
This has come up for various crashes in the past. There is an open issue for resolving the underlying cause of restore tabs showing up.
Cc: derat@chromium.org
Cc: jdufault@chromium.org
Labels: -Type-Bug-Security -Restrict-View-Google -Pri-3 Stability-Crash Pri-1 Type-Bug
Summary: Chrome crashed while locking screen (was: OS not locked after wake from closed lid)
 Issue 867970  tracks a fallback (which I'll try to finish up), but it'll be a poor user experience: the user will be signed out and the system will shut down.

Please make sure that you're investigating these Chrome crashes since they need to be fixed. You should be able to find crashes from the user's device using the client ID (which you can get from a feedback report).
Cc: -jdufault@chromium.org r...@chromium.org mnissler@chromium.org
Owner: jdufault@chromium.org
We should prioritize the work on re-working how lock and suspend interact that we were planning.

#6: I haven't heard of that. Is there a bug or doc with more detail?
I was referring to the discussion we had on  issue 867970  - didn't realize you had already started work on it :)

Labels: Hotlist-auth-polish
Status: WontFix (was: Assigned)
Likely fixed by some other bug, nothing directly actionable here, closing as WontFix.

Sign in to add a comment