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

Issue 896436 link

Starred by 2 users

Issue metadata

Status: Closed
Owner:
Closed: Nov 2
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Pixelbook close-lid+open-lid causes Chrome to crash and lose work in progress.

Project Member Reported by shelat@google.com, Oct 17

Issue description

Google Chrome	71.0.3578.8 (Official Build) dev (64-bit)
Revision	a2c2b8f674ee3b7372bc87891e04a14a0e51e812-refs/branch-heads/3578@{#14}
Platform	11151.4.0 (Official Build) dev-channel eve-arcnext
Firmware Version	Google_Eve.9584.174.0
Customization ID	GOOGLE-EVE
ARC	5069604
JavaScript	V8 7.1.302.2
Flash	31.0.0.122 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS x86_64 11151.4.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.8 Safari/537.36



Steps To Reproduce:
(1) Open several tabs in Chrome, gmail, etc.
(2) Close the lid of the pixelbook, thereby putting the machine to sleep. (Or, while on a GVC in preso mode, start talking about a slide, and then machine goes to sleep.)
(3) Open the lid to get back to work.  Poof! Chrome has crashed. All windows gone.  Offer to "restore session" sometimes works, and sometimes does not restore the session.

Expected Result:
Just as earlier as 2 days ago, the standard feature of sleeping, waking, and getting back to work was functional. A recent change has broken this.


Actual Result:

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)

Always on my device.

What is the impact to the user, and is there a workaround? If so, what is
it?

Poof! work gone.


Please provide any additional information below. Attach a screen shot or
log if possible.

For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Owner: afakhry@chromium.org
afakrhy@ let's triage this and decide on where this crash belongs
Cc: ovanieva@google.com osh...@chromium.org shelat@google.com
Labels: Needs-Feedback
shelat@ Does this still happen? Do you have any IDs in your chrome://crashes page?
Upgrade to .21 on dev fixed this issue
Thanks,
a
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 2

Cc: afakhry@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Closed (was: Unconfirmed)

Sign in to add a comment