Chrome crashed when locking screen
Reported by
mguage...@tidalpay.com,
Jan 31 2017
|
||||||||
Issue descriptionChrome Version: 55.0.2883.105 OS: Chrome OS 8872.76.0 (Official Build) stable-channel panther Google_Panther.4920.24.26 Can you reproduce this crash? Unable to reproduce reliably, reported by others within the organization. What steps will reproduce this crash (or if it's not reproducible, what were you doing just before the crash)? (1) Had Gmail, Google Drive, Time off Manager open (2) Walked away for a few minutes (3) Chromebox went to sleep after 5 mins, but crashed upon signing back in. *Please note that issues filed with no information filled in above will be marked as WontFix*
,
Nov 3 2017
,
Nov 3 2017
The system didn't suspend; it just turned the screen off and attempted to lock it: --- [0131/113906:INFO:state_controller.cc(89)] Turning screen off after 15m [0131/113906:INFO:display_power_setter.cc(80)] Asking Chrome to turn all displays off [0131/113906:INFO:daemon.cc(1337)] Chrome is using normal display mode [0131/113916:INFO:state_controller.cc(89)] Locking screen after 15m10s --- 2017-01-31T11:39:16.960775-06:00 INFO session_manager[15115]: [INFO:session_manager_impl.cc(542)] LockScreen() method called. 2017-01-31T11:39:16.993619-06:00 INFO kernel: [146504.435330] traps: chrome[15138] trap invalid opcode ip:7f532d059321 sp:7ffffb0eef98 error:0 in chrome[7f532a14d000+6c9b000] 2017-01-31T11:39:17.007500-06:00 WARNING crash_reporter[31145]: [user] Received crash notification for chrome[15138] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly) 2017-01-31T11:39:17.038815-06:00 ERR session_manager[15115]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.LibCrosServiceInterface.LockScreen: object_path= /org/chromium/LibCrosService: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) 2017-01-31T11:39:17.245228-06:00 INFO session_manager[15115]: [INFO:child_exit_handler.cc(77)] Handling 15138 exit. 2017-01-31T11:39:17.245248-06:00 ERR session_manager[15115]: [ERROR:child_exit_handler.cc(85)] Exited with signal 4 2017-01-31T11:39:17.245253-06:00 INFO session_manager[15115]: [INFO:session_manager_service.cc(296)] Exiting process is chrome. 2017-01-31T11:39:17.245257-06:00 INFO session_manager[15115]: [INFO:browser_job.cc(116)] Terminating process group: Ensuring browser processes are gone. 2017-01-31T11:39:17.245262-06:00 INFO session_manager[15115]: [INFO:system_utils_impl.cc(87)] Sending 9 to -15138 as 1000 2017-01-31T11:39:17.400373-06:00 ERR session_manager[15115]: [ERROR:session_manager_service.cc(314)] Choosing to end session rather than restart browser. 2017-01-31T11:39:17.400500-06:00 INFO session_manager[15115]: [INFO:session_manager_service.cc(611)] SessionManagerService quitting run loop 2017-01-31T11:39:17.400614-06:00 INFO session_manager[15115]: [INFO:session_manager_service.cc(236)] SessionManagerService exiting --- I'm sorry that it took so long to get a reply. Are you still seeing the issue?
,
Dec 11 2017
No feedback was received in the last 30 days from reporter "mguagenti@tidalpay.com", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by nyerramilli@chromium.org
, Feb 1 2017