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

Issue 644876 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

tabs spinning after suspend/resume & kernel-warning observed sometimes

Project Member Reported by helenzhang@google.com, Sep 7 2016

Issue description

Google Chrome : 53.0.2785.100 (Official Build) beta (64-bit)
Platform : 8530.80.0 (Official Build) beta-channel

What steps will reproduce the problem?
(1) Sign in with external monitor conncted (here ACER 
(2) Run "powerd_dbus_suspend" under shell crosh terminal 
(3) Resume 
(do not remember exact steps) 

What is the expected output? 
Everything resume properly 

What do you see instead?
- Observe browser tabs spinning, nothing works e.g. Files manager/Feedback can not launch. 
- A page popup saying "pages not responsible ..." ( see screenshot attached) 
- only VT2 works 
- kernel warnings at /var/spool/crash 

crash id:
39457c1500000000, 4a95726e00000000

- Reproduce once. (remember saw similar issue on samus, but didn't get log) 
- Unable to reproduce it after rebooting the device. 

 
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 8 2016

Labels: Hotlist-Google
Cc: derat@chromium.org snanda@chromium.org
Labels: Proj-Sezter
Summary: tabs spinning after suspend/resume & kernel-warning observed sometimes (was: [link] tabs spinning after suspend/resume & kernel-warning observed (ONCE) )
Observed the same issue ONCE on setzer in ChromeOS 8530.81.0, 53.0.2785.103 too . 

Possible steps causing it: 
- run 'powerd_dbus_suspend'
- unplug/replug external peripherals & external monitor 
- resume 
- notice that up arrow key does not work on crosh running 'powerd_dbus_suspend'
- open a new tab 
- new tab spinning, anything else does not work, only VT2 works. 
- No kernel warning on setzer. 

Unable to reproduce it after rebooting the device. 
Notice both setzer and link were in low battery power status. 

setzer log&screenshot:
https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/644876/


Comment 4 by derat@chromium.org, Sep 8 2016

Cc: chirantan@chromium.org
Components: -OS>Kernel Internals OS>Systems
Hmm, maybe a problem with renderers not getting unfrozen?
Components: -Internals

Sign in to add a comment