The behavior you're describing sounds like a crash. Is there an ID in chrome://crashes?

Has been awhile since it happened to me, have been distracted because of a different, unrelated issue, I'm also on beta 55 which might have something to due with me not having issue.

Nothing showed up in chrome://crashes

From personal and cases from other people, if there is music playing or sound happening when it does happen, the music doesn't cease and it acts like nothing is going on at all.

I've been having the same problem with the blacking out as well. It started about 2 weeks after I bought the laptop (mid October). I was on the stable channel. I was advised to switch to beta. The became less frequent. Eventually I switched to the Dev channel, again it wasn't as frequent. 

Today my computer did the blacking out sequence for about 5 minutes. Here's what happened:

I was downloading a folder of music off of drive (appx 700 songs via the file manager). It got to 400 songs left and the computer slowed down to a crawl, I tried cancelling the download, but it wouldn't cancel. I tried to power down the computer (by selecting the power button in the notification tray) and then it went black (I thought it shut down), I pressed a key, it came on for a second, then blacked out again (it did this twice) then it came back to the login screen. I logged in and the computer blacked out again then it completely restarted. Once I logged back in, Chrome started it did not load last visited pages, nor did it give a restore banner. I did report the crash via the alt+shift+i and explained this as well.

I have a Samsung XE500C13-K01US Chromebook 3 running the following: 

8992.0.0 (Official Build) dev-channel celes
Firmware
Google_Celes.7287.92.60
Channel
Currently on dev

#3: Thanks for all the feedback reports! I'm including comments about each below:

----

http://feedback/#/Report/13283967975
"Using file manager and switched to chrome. Blacked out for 2 seconds."

I think that this was a GPU hang. Unfortunately, it looks like you don't have crash reporting enabled:

2016-11-09T21:58:26.781792-05:00 INFO kernel: [ 3073.707252] [drm] stuck on render ring
2016-11-09T21:58:26.811969-05:00 INFO kernel: [ 3073.738603] [drm] GPU HANG: ecode 8:0:0x85dffffb, in chrome [2300], reason: Ring hung, action: reset
2016-11-09T21:58:26.811998-05:00 INFO kernel: [ 3073.738624] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2016-11-09T21:58:26.812012-05:00 INFO kernel: [ 3073.738639] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2016-11-09T21:58:26.812022-05:00 INFO kernel: [ 3073.738653] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2016-11-09T21:58:26.812032-05:00 INFO kernel: [ 3073.738668] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
2016-11-09T21:58:26.812041-05:00 INFO kernel: [ 3073.738682] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2016-11-09T21:58:26.812048-05:00 WARNING kernel: [ 3073.738747] ------------[ cut here ]------------
2016-11-09T21:58:26.812060-05:00 WARNING kernel: [ 3073.738767] WARNING: CPU: 0 PID: 22479 at /mnt/host/source/src/third_party/kernel/v3.18/drivers/gpu/drm/i915/intel_display.c:11178 intel_mmio_flip_work_func+0x6d/0x315()
2016-11-09T21:58:26.812143-05:00 WARNING kernel: [ 3073.738789] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
2016-11-09T21:58:26.812183-05:00 WARNING kernel: [ 3073.738807] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat uinput i2c_dev ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat snd_soc_sst_cht_bsw_rt5645 rfcomm memconsole_x86_legacy memconsole snd_hda_codec_hdmi xt_mark snd_intel_sst_acpi snd_soc_sst_acpi snd_hda_intel snd_intel_sst_core snd_hda_codec snd_hwdep snd_soc_rt5645 snd_soc_sst_mfld_platform bridge snd_hda_core snd_soc_rl6231 stp llc fuse zram ccm ip6table_filter iwlmvm iwlwifi iwl7000_mac80211 cfg80211 btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core joydev snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ppp_async ppp_generic slhc tun
2016-11-09T21:58:26.812193-05:00 WARNING kernel: [ 3073.738993] CPU: 0 PID: 22479 Comm: kworker/0:2 Tainted: G        W      3.18.0-13399-g5b88d55 #1
2016-11-09T21:58:26.812202-05:00 WARNING kernel: [ 3073.739035] Hardware name: GOOGLE Celes, BIOS Google_Celes.7287.92.35 05/29/2016
2016-11-09T21:58:26.812209-05:00 WARNING kernel: [ 3073.739052] Workqueue: events intel_mmio_flip_work_func
2016-11-09T21:58:26.812301-05:00 WARNING kernel: [ 3073.739097]  0000000000000000 000000002aec7e2e ffff8800770bbcd8 ffffffffb2a92687
2016-11-09T21:58:26.812355-05:00 WARNING kernel: [ 3073.739126]  0000000000000000 ffff8800770bbd30 ffff8800770bbd18 ffffffffb2462c3c
2016-11-09T21:58:26.812369-05:00 WARNING kernel: [ 3073.739144]  ffff8800770bbce8 ffffffffb27b9cb8 ffff8800779a6300 ffff8800569f8a40
2016-11-09T21:58:26.812376-05:00 WARNING kernel: [ 3073.739162] Call Trace:
2016-11-09T21:58:26.812386-05:00 WARNING kernel: [ 3073.739176]  [<ffffffffb2a92687>] dump_stack+0x4e/0x71
2016-11-09T21:58:26.812395-05:00 WARNING kernel: [ 3073.739190]  [<ffffffffb2462c3c>] warn_slowpath_common+0x81/0x9b
2016-11-09T21:58:26.812404-05:00 WARNING kernel: [ 3073.739204]  [<ffffffffb27b9cb8>] ? intel_mmio_flip_work_func+0x6d/0x315
2016-11-09T21:58:26.812413-05:00 WARNING kernel: [ 3073.739218]  [<ffffffffb2462cab>] warn_slowpath_fmt+0x55/0x6b
2016-11-09T21:58:26.812422-05:00 WARNING kernel: [ 3073.739231]  [<ffffffffb27b9cb8>] intel_mmio_flip_work_func+0x6d/0x315
2016-11-09T21:58:26.812467-05:00 WARNING kernel: [ 3073.739247]  [<ffffffffb2482788>] ? finish_task_switch+0x5b/0xba
2016-11-09T21:58:26.812481-05:00 WARNING kernel: [ 3073.739262]  [<ffffffffb2477983>] process_one_work+0x176/0x2d4
2016-11-09T21:58:26.812491-05:00 WARNING kernel: [ 3073.739275]  [<ffffffffb2478308>] worker_thread+0x1ec/0x2bf
2016-11-09T21:58:26.812500-05:00 WARNING kernel: [ 3073.739287]  [<ffffffffb247811c>] ? rescuer_thread+0x2db/0x2db
2016-11-09T21:58:26.812508-05:00 WARNING kernel: [ 3073.739300]  [<ffffffffb247c3d2>] kthread+0x10e/0x116
2016-11-09T21:58:26.812517-05:00 WARNING kernel: [ 3073.739313]  [<ffffffffb247c2c4>] ? __kthread_parkme+0x67/0x67
2016-11-09T21:58:26.812525-05:00 WARNING kernel: [ 3073.739326]  [<ffffffffb2a9782c>] ret_from_fork+0x7c/0xb0
2016-11-09T21:58:26.812569-05:00 WARNING kernel: [ 3073.739338]  [<ffffffffb247c2c4>] ? __kthread_parkme+0x67/0x67
2016-11-09T21:58:26.812582-05:00 WARNING kernel: [ 3073.739349] ---[ end trace 95fa6beef3b3b8a8 ]---
2016-11-09T21:58:26.817888-05:00 NOTICE kernel: [ 3073.744153] drm/i915: Resetting chip after gpu hang
2016-11-09T21:58:26.997298-05:00 INFO crash_reporter[25205]: Ignoring - Non-developer image and no consent given.

----

http://feedback/#/Report/13610229067
"Blacked out for 3 seconds or so."

This looks like another GPU hang:

2016-11-17T13:30:16.229488-05:00 INFO kernel: [52098.703246] [drm] stuck on render ring
2016-11-17T13:30:16.264029-05:00 INFO kernel: [52098.734815] [drm] GPU HANG: ecode 8:0:0xef9ffffd, in chrome [1185], reason: Ring hung, action: reset
2016-11-17T13:30:16.264085-05:00 INFO kernel: [52098.734835] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2016-11-17T13:30:16.264104-05:00 INFO kernel: [52098.734850] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2016-11-17T13:30:16.264119-05:00 INFO kernel: [52098.734864] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2016-11-17T13:30:16.264132-05:00 INFO kernel: [52098.734878] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
2016-11-17T13:30:16.264143-05:00 INFO kernel: [52098.734892] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2016-11-17T13:30:16.264153-05:00 NOTICE kernel: [52098.738494] drm/i915: Resetting chip after gpu hang
2016-11-17T13:30:16.449723-05:00 INFO crash_reporter[26332]: Ignoring - Non-developer image and no consent given.

----

http://feedback/#/Report/13942946499
"Black screen for 3 seconds, tapped a key and co mputer rebooted."
Kernel panic at 2016-11-25 21:39:25; system rebooted.

----

http://feedback/#/Report/14108363351
"Just woke up computer, I had it asleep for a day or so. Had chrome open and computer went black for 5 seconds and had a hard time coming back up. Chrome browser restarted."
Chrome segfaulted at 2016-11-30 09:14:37, shortly after the system resumed.

----

http://feedback/#/Report/21897195002
"... Screen blacked out for about 10 seconds. Came back to normal when the screen came back on."

This looks like a different GPU issue:

2016-11-03T09:34:43.958283-04:00 ERR kernel: [ 2780.269049] [drm:i9xx_set_fifo_underrun_reporting] *ERROR* pipe A underrun
2016-11-03T09:34:43.958309-04:00 ERR kernel: [ 2780.269077] [drm:intel_cpu_fifo_underrun_irq_handler] *ERROR* CPU pipe A FIFO underrun

This feedback report is from 8872.27.0. I think that this problem was tracked at  issue 652110  and fixed in 8743.81.0, so I'm at a loss for why it still showed up.

----

So I unfortunately don't see anything systemic here; it's a bunch of different unrelated issues. Would you mind enabling crash reporting (described at https://support.google.com/chrome/answer/96817?co=GENIE.Platform%3DDesktop&hl=en) so that crashes will be uploaded and someone can take a look at them? If chrome://crashes still lists some entries, you may be able to upload the previous crashes from there, too.

Stephane, can you comment on the GPU hangs and "pipe A underrun" / "CPU pipe A FIFO underrun" errors above, too?

#4, I did turn it on that day (nov 30th) and it did something similar Dec 1st (according to the crash reports). I just looked on the chrome://crashes and it lists two reports. The reports stated that they've been submitted. 

I'm sorry I'm not incredibly knowledgeable on how to do things like that with chromebooks (I just got mine in the middle of Oct of this year), but I do follow instructions well. Just tell me what to do, and I'll do my best to do it. 

I apologize for not responding sooner, I thought I'd get an email notification when there was a reply.

(You should get email notifications if you've clicked the star icon near the top-left corner of the page.)

Thanks, I see the two crashes that were uploaded.

One of them is a Chrome crash that looks like it's already tracked at  issue 663943 . I've added some people who might be able to look into it.

The other crash in is code for running Android apps. I didn't see a bug tracking it, so I've filed issue 671019.

You should be able to star either of those issues to receive updates.

Thank you for telling me how to get email notifications.

My Chromebook blacked out again. I reported it.

Do you want me to put ID 663943 & 671019 when I experience these issues as well?

#7: Thanks, and no need to put the bug IDs in the descriptions.

http://feedback/#/Report/22694671850 is the latest report. It looks like it was a GPU issue again, and the same as one of the reports I looked at in comment #4:

2016-12-04T12:23:46.837113-05:00 INFO kernel: [ 5384.703254] [drm] stuck on render ring
2016-12-04T12:23:46.864124-05:00 INFO kernel: [ 5384.730290] [drm] GPU HANG: ecode 8:0:0xef9ffffd, in Chrome_InProcGp [21498], reason: Ring hung, action: reset
2016-12-04T12:23:46.864149-05:00 INFO kernel: [ 5384.730312] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2016-12-04T12:23:46.864156-05:00 INFO kernel: [ 5384.730328] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2016-12-04T12:23:46.864161-05:00 INFO kernel: [ 5384.730342] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2016-12-04T12:23:46.864166-05:00 INFO kernel: [ 5384.730357] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
2016-12-04T12:23:46.864171-05:00 INFO kernel: [ 5384.730372] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2016-12-04T12:23:46.864175-05:00 WARNING kernel: [ 5384.730438] ------------[ cut here ]------------
2016-12-04T12:23:46.864181-05:00 WARNING kernel: [ 5384.730460] WARNING: CPU: 1 PID: 23434 at /mnt/host/source/src/third_party/kernel/v3.18/drivers/gpu/drm/i915/intel_display.c:11178 intel_mmio_flip_work_func+0x6d/0x315()
2016-12-04T12:23:46.864193-05:00 WARNING kernel: [ 5384.730482] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, &mmio_flip->i915->rps.mmioflips))
2016-12-04T12:23:46.864212-05:00 WARNING kernel: [ 5384.730500] Modules linked in: ip6t_REJECT nf_reject_ipv6 xt_TCPMSS ip6table_mangle veth nls_iso8859_1 nls_cp437 vfat fat ccm uinput rfcomm iwlmvm ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 snd_hda_codec_hdmi nf_nat iwlwifi snd_soc_sst_cht_bsw_rt5645 memconsole_x86_legacy memconsole snd_hda_intel iwl7000_mac80211 snd_hda_codec snd_intel_sst_acpi snd_soc_sst_acpi snd_intel_sst_core xt_mark snd_hwdep snd_hda_core snd_soc_sst_mfld_platform snd_soc_rt5645 snd_soc_rl6231 bridge stp llc fuse zram cfg80211 ip6table_filter snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device btusb btrtl btbcm btintel bluetooth joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core
2016-12-04T12:23:46.864217-05:00 WARNING kernel: [ 5384.730709] CPU: 1 PID: 23434 Comm: kworker/1:0 Tainted: G        W      3.18.0-13492-g308c6f5 #1
2016-12-04T12:23:46.864222-05:00 WARNING kernel: [ 5384.730724] Hardware name: GOOGLE Celes, BIOS Google_Celes.7287.92.60 11/06/2016
2016-12-04T12:23:46.864226-05:00 WARNING kernel: [ 5384.730740] Workqueue: events intel_mmio_flip_work_func
2016-12-04T12:23:46.864230-05:00 WARNING kernel: [ 5384.730752]  0000000000000000 00000000fc0b67f6 ffff880006e8bcd8 ffffffffbd89a6a7
2016-12-04T12:23:46.864235-05:00 WARNING kernel: [ 5384.730772]  0000000000000000 ffff880006e8bd30 ffff880006e8bd18 ffffffffbd262c3c
2016-12-04T12:23:46.864239-05:00 WARNING kernel: [ 5384.730791]  ffff880006e8bce8 ffffffffbd5b79f1 ffff880040507a80 ffff880035345780
2016-12-04T12:23:46.864242-05:00 WARNING kernel: [ 5384.730811] Call Trace:
2016-12-04T12:23:46.864248-05:00 WARNING kernel: [ 5384.730827]  [<ffffffffbd89a6a7>] dump_stack+0x4e/0x71
2016-12-04T12:23:46.864300-05:00 WARNING kernel: [ 5384.730843]  [<ffffffffbd262c3c>] warn_slowpath_common+0x81/0x9b
2016-12-04T12:23:46.864308-05:00 WARNING kernel: [ 5384.730862]  [<ffffffffbd5b79f1>] ? intel_mmio_flip_work_func+0x6d/0x315
2016-12-04T12:23:46.864313-05:00 WARNING kernel: [ 5384.730878]  [<ffffffffbd262cab>] warn_slowpath_fmt+0x55/0x6b
2016-12-04T12:23:46.864317-05:00 WARNING kernel: [ 5384.730893]  [<ffffffffbd5b79f1>] intel_mmio_flip_work_func+0x6d/0x315
2016-12-04T12:23:46.864322-05:00 WARNING kernel: [ 5384.730909]  [<ffffffffbd28278e>] ? finish_task_switch+0x5b/0xba
2016-12-04T12:23:46.864326-05:00 WARNING kernel: [ 5384.730925]  [<ffffffffbd277983>] process_one_work+0x176/0x2d4
2016-12-04T12:23:46.864330-05:00 WARNING kernel: [ 5384.730940]  [<ffffffffbd278308>] worker_thread+0x1ec/0x2bf
2016-12-04T12:23:46.864334-05:00 WARNING kernel: [ 5384.730954]  [<ffffffffbd27811c>] ? rescuer_thread+0x2db/0x2db
2016-12-04T12:23:46.864361-05:00 WARNING kernel: [ 5384.730968]  [<ffffffffbd27c3d2>] kthread+0x10e/0x116
2016-12-04T12:23:46.864368-05:00 WARNING kernel: [ 5384.730981]  [<ffffffffbd27c2c4>] ? __kthread_parkme+0x67/0x67
2016-12-04T12:23:46.864372-05:00 WARNING kernel: [ 5384.730996]  [<ffffffffbd89f82c>] ret_from_fork+0x7c/0xb0
2016-12-04T12:23:46.864377-05:00 WARNING kernel: [ 5384.731038]  [<ffffffffbd27c2c4>] ? __kthread_parkme+0x67/0x67
2016-12-04T12:23:46.864381-05:00 WARNING kernel: [ 5384.731064] ---[ end trace 7ffcf774a05a4cea ]---
2016-12-04T12:23:46.870766-05:00 NOTICE kernel: [ 5384.736187] drm/i915: Resetting chip after gpu hang

Let's use this bug to track that particular problem. Stephane, is this something that you're already aware of?

+Intel for gpu crashes on braswell. I'll also try to find a celes somewhere.

This is being tracked internally at https://code.google.com/p/chrome-os-partner/issues/detail?id=57702 (see comment#270 onwards) .. 

I got a celes, tried a few things (webgl, youtube etc.) but couldn't repro a gpu hang. Do you have anything specific I should try to repro?

#12: Unfortunately, it sounds (both from these feedback reports and from the partner bug) like it just happens periodically during normal use. I haven't heard of anything that triggers it.

Typing seemed to be one of the causes when I had the issue, but yes, it does seem to be semi-random with no specific trigger to do it on command unfortunately.

#14, this problem usually occurs randomly whenever I use chrome. I've not had this issue occur when I was typing.

around timestamp 10:37 is when it happened. This is my first one in forever, was listening to youtube in the background, had gmail and 3 gdocs open. 

Deleted: messages.txt 1.3 MB

messages.txt 1.3 MB View Download

Computer blacked out about a minute ago. I forgot the bug ID, but I did say it blacked out in the first line. 

I was running chrome, file manager and stock music player. The music player was at the end of a song and I clicked to close it and that's when the black out occurred. Chrome was in focus behind the music player. File manage was minimized. After hitting the space bar several times, the computer came back to normal, however it didn't restart the file manager, nor the tab I had up (had restore banner). I was on battery (if that matters). I also have the Weather Underground app running in the background.

Oh, and I was transferring a mp3 to drive via file manager.

#17: Thanks, feedback report is at http://feedback/#/Report/50580882106. There are a lot of Android crashes similar to this, but I don't know if they're related:

016-12-21T22:18:10.210812-05:00 INFO kernel: [31322.661823] main[6691]: segfault at bcce96a5 ip 00000000f31ddae0 sp 00000000ff807b30 error 4 in libart.so[f2dd8000+885000]
2016-12-21T22:18:10.238859-05:00 WARNING crash_reporter[6726]: [user] Received crash notification for app_process32[6691] sig 11, user 655360 (ignoring - PID filtered out)
2016-12-21T22:18:10.239928-05:00 WARNING crash_reporter[6726]: [ARC] Received crash notification for zygote[6691] sig 11, user 655360 (handling)

Black out happened again. It seems to be triggered by the stock music player. The last two times it blacked out was after trying to exit the program. Probably unrelated, but even though I didn't have the browser open, once it came back, it was opened and showed the restore banner. This time the black out lasted twice as long and wouldn't respond to tapping on the keys or clicking the track pad.

#19: Thanks, looks like Chrome crashed:

2016-12-22T22:24:50.736363-05:00 WARNING crash_reporter[650]: Received crash notification for chrome[5909] user 1000 (called directly)
2016-12-22T22:24:51.340757-05:00 INFO kernel: [46730.271813] chrome[5909]: segfault at 0 ip 00007f5cbef859cc sp 00007ffcb09ed530 error 4 in chrome[7f5cb8ef4000+6f3f000]
2016-12-22T22:24:51.392918-05:00 WARNING crash_reporter[672]: [user] Received crash notification for chrome[5909] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2016-12-22T22:24:51.395172-05:00 WARNING crash_reporter[672]: [ARC] Received crash notification for chrome[5909] sig 11, user 1000 (ignoring - crash origin is not ARC)
...
2016-12-22T22:24:51.770810-05:00 INFO session_manager[1009]: [INFO:child_exit_handler.cc(77)] Handling 5909 exit.
2016-12-22T22:24:51.770863-05:00 ERR session_manager[1009]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 11
2016-12-22T22:24:51.770937-05:00 INFO session_manager[1009]: [INFO:session_manager_service.cc(301)] Exiting process is chrome.

It's probably unrelated to the GPU hangs that were discussed here earlier. If you paste the recent crash IDs listed at chrome://crashes, it should be possible to either find a bug already tracking the crash or file a new bug if needed.

Chormebook blacked out again. I caught it on video (https://drive.google.com/file/d/0Bx9Y93NE8tjjZ0c3V01hdlo1bGs/view?usp=sharing) I was trying to show my friend the "OK Google" Command. 

Running:
PlayStore
File Manager

If you watch the video, I say the command and just pick something random to look up and it brings up the search engine and right before it speaks a definition, it blacks out. I tried tapping the space bar and track pad and eventually comes back. It shows the file manager but no files inside.

I also suffered this issue in some CrOS BSW platforms with 9127.0.0 (Official Build) dev-channel (by guest account).

It's easy to restart chrome browser for above case,

Kernel message,
...
2016-12-29T12:49:41.703496+08:00 ERR cras_server[2577]: pcm_avail returned frames larger than buf_size: chtrt5650: :0,0: 205056 > 204800 for 1 times
2016-12-29T12:49:41.789835+08:00 WARNING crash_reporter[5905]: Could not load the device policy file.
2016-12-29T12:49:41.792810+08:00 WARNING crash_reporter[5905]: Received crash notification for chrome[4137] user 1000 (called directly)
2016-12-29T12:49:41.924275+08:00 INFO kernel: [  380.740802] BrowserBlocking[4188]: segfault at 0 ip 00005e9889b19157 sp 00007e950f446880 error 4 in chrome[5e9888b73000+6f35000]
2016-12-29T12:49:41.945046+08:00 WARNING crash_reporter[5923]: Could not load the device policy file.
2016-12-29T12:49:41.945735+08:00 WARNING crash_reporter[5923]: [user] Received crash notification for chrome[4137] sig 11, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2016-12-29T12:49:42.023251+08:00 DEBUG kernel: [  380.840131] [drm:intel_set_memory_cxsr] memory self-refresh is disabled
2016-12-29T12:49:42.030236+08:00 DEBUG kernel: [  380.846703] [drm:intel_set_memory_cxsr] memory self-refresh is disabled
2016-12-29T12:49:42.030273+08:00 DEBUG kernel: [  380.846740] [drm:edp_panel_vdd_on] Turning eDP port C VDD on
2016-12-29T12:49:42.030298+08:00 DEBUG kernel: [  380.846754] [drm:edp_panel_vdd_on] PP_STATUS: 0x80000008 PP_CONTROL: 0xabcd000f
2016-12-29T12:49:42.030306+08:00 DEBUG kernel: [  380.846768] [drm:intel_edp_backlight_off]
2016-12-29T12:49:42.045654+08:00 ERR cras_server[2577]: fetch err: -32 for 20000
2016-12-29T12:49:42.046126+08:00 INFO session_manager[1467]: [INFO:child_exit_handler.cc(77)] Handling 4137 exit.
2016-12-29T12:49:42.046159+08:00 ERR session_manager[1467]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 11
2016-12-29T12:49:42.046191+08:00 INFO session_manager[1467]: [INFO:session_manager_service.cc(301)] Exiting process is chrome.
2016-12-29T12:49:42.046281+08:00 INFO session_manager[1467]: [INFO:browser_job.cc(149)] Terminating process group: Ensuring browser processes are gone.
...

UI log,
...
[1:10:1229/124853.629117:ERROR:ffmpeg_demuxer.cc(378)] Format conversion failed.
[1:10:1229/124920.521483:ERROR:ffmpeg_demuxer.cc(378)] Format conversion failed.
_sys_cr_finished
System crash-reporter failed to process crash report.
Report Id:
[1229/124942.599274:WARNING:diagnostics_writer.cc(209)] [FAIL] 002 SQLiteIntegrityCookie (File not found)
[1229/124942.602954:WARNING:diagnostics_writer.cc(209)] Finished 18 tests.
[1229/124942.603043:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Install type
[1229/124942.603078:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Chrome version test
[1229/124942.603111:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: User data path
[1229/124942.603145:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Local state path
[1229/124942.603178:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: App dictionaries directory path
[1229/124942.603229:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Resources path
[1229/124942.603266:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Available disk space
[1229/124942.603310:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: User preferences integrity
[1229/124942.603343:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Local state integrity
[1229/124942.603375:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Bookmark file
[1229/124942.603408:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Web Data database
[1229/124942.603440:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Cookie database
[1229/124942.603473:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Favicons database
[1229/124942.603505:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: History database
[1229/124942.603538:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Top Sites database
[1229/124942.603570:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: Database tracker database
[1229/124942.603604:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: NSS certificate database
[1229/124942.603660:WARNING:diagnostics_writer.cc(209)] Finished Recovery for: NSS Key database
[1229/124942.603684:WARNING:diagnostics_writer.cc(209)] Finished All Recovery operations.
[5927:5927:1229/124944.299922:ERROR:wallpaper_manager.cc(758)] User is ephemeral or guest! Fallback to default                                                                                                                                                                             wallpaper.
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/va/drivers/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
[5927:5927:1229/124945.170407:ERROR:CONSOLE(305)] "Unexpected condition on chrome://newtab/: Could not find va                                                                                                                                                                            lue for enterpriseInfoMessage", source: chrome://newtab/ (305)
[5927:5927:1229/124945.171409:ERROR:CONSOLE(305)] "Unexpected condition on chrome://newtab/: [undefined] (ente                                                                                                                                                                            rpriseInfoMessage) is not a string", source: chrome://newtab/ (305)
[5927:5927:1229/124945.228795:ERROR:CONSOLE(305)] "Unexpected condition on chrome://newtab/: Could not find va                                                                                                                                                                            lue for enterpriseLearnMore", source: chrome://newtab/ (305)
[5927:5927:1229/124945.229456:ERROR:CONSOLE(305)] "Unexpected condition on chrome://newtab/: [undefined] (ente                                                                                                                                                                            rpriseLearnMore) is not a string", source: chrome://newtab/ (305)
[5927:5927:1229/124945.230051:ERROR:CONSOLE(305)] "Unexpected condition on chrome://newtab/: Could not find va                                                                                                                                                                            lue for enterpriseInfoHintLink", source: chrome://newtab/ (305)
...

Continue with #22 about its test-case,
1) Multi tab for rendering host on cnn.com/foxnews.com/nba.com/yahoo.com/nbc.com
2) 4K h.264 infinite video playback (MPEG-4-Base, Version 2, 3840x2160)

I've been having issues with my stock music player, so as suggested by a member of the Google forum, I power washed and switched back to stable. Within 5 minutes of being on stable, the computer blacked out twice. I was using the stock music player, Chrome, and file manager. I don't know if this is relevant, but I was playing music off my SD card. Also, after restarting and trying the music player again, it slowed it down to a crawl, played the music and froze. I had to hold the power button for a good minute before it would shut down.

Happening to me also on the Flip C100PA on both the Dev and Canary channels (unsure about Stable or Beta). Here's a set of ids from just today.

Crash ID ChromeOS (Server ID: cdabd87080000000)
Crash ID Chrome (Server ID: b76f607a80000000)
Crash ID Chrome (Server ID: 335f587080000000)
Crash ID Chrome (Server ID: 84a3287080000000)
Crash ID Chrome (Server ID: 4beed26580000000)
Crash ID Chrome (Server ID: ce5cd26580000000)
Crash ID Chrome (Server ID: 86d8487080000000)
Crash ID Chrome (Server ID: aa969fba80000000)
Crash ID ChromeOS_ARC (Server ID: f24b1fba80000000)
Crash ID ChromeOS_ARC (Server ID: cb011fba80000000)
Crash ID ChromeOS_ARC (Server ID: 47db087080000000)
Crash ID ChromeOS_ARC (Server ID: 937d926580000000)
Crash ID ChromeOS_ARC (Server ID: 085d0fba80000000)
Crash ID ChromeOS_ARC (Server ID: 64e40fba80000000)
Crash ID ChromeOS_ARC (Server ID: 0be3f7ba80000000)
Crash ID ChromeOS_ARC (Server ID: ff99d07080000000) 

All of them caused the screen to suddenly go black for 5-15 seconds before showing the restore banner. Interestingly, there was a lot of ARC ones but I haven't used any of the Android apps installed for at least 2 or 3 days.

 Issue 662278  has been merged into this issue.

new motherboard sorted mine

After updating to version beta 57 on my R11 the black screen part of the issue went away.

Instead the whole thing froze for a few seconds, then went back to normal, most of the time cutting off my wifi on the device, at first I thought the wifi cutting off was my wifi card, (I was having issues with that in the past) but after switching to stable I have had no issues with GPU hangs or wifi drops whatsoever.

On stable 55, before the update, I had no issues with black screen, then as soon at 56 hit it started happening again, though not as severe as in 57.

Only when youtube is open and playing.

On stable. Computer blacked out when trying to access the SD cared from 3rd party music player. Blacked out ~30 seconds. When it came back Chrome gave the restore banner and the music player was still running.

I did submit a report under this bug ID.

a bunch of these crashes are in the ui compositor:

84a3287080000000
4beed26580000000
ce5cd26580000000

a bunch are in android, we should probably keep them in a separate bug.

Dave since you are a good owner for both can you take a look?

The vsync observer issue is likely a duplicate of  issue 679787 . We had a bug in mid Jan where we were seeing crashes because we failed to remove the vsync observer. These crashes seem to be from the period. That issue was fixed 10 weeks ago. Please assign back to me if this still happening today.

I've been able to reliably get a GPU "black screen issue" on this site here http://lucafraga.github.io/TrippySnake/ on my R11

Deleted: messages.txt 2.5 MB

messages.txt 2.5 MB View Download

#33:  Thanks for the site.  I can reproduce GPU hangs with this site as well.  I've captured the problem with a debug build and forwarded logs to the upstream graphics team for further analysis.

#33:  GPU hangs have been traced to the following patch in chromiumos-overlay in R52-8244.0.0:

d880e31 media-libs/mesa: Updated Mesa to c3b88cc2c15f19e748c9c406e9ab053975adab7e

#33:  GPU hangs are NOT reproducible on R59-9405.0.0, which is ToT as of yesterday.  It looks like the problem went away starting with R57-9088.0.0.  Could you please confirm if you were using an older build when you saw the problem?

The bisect of MESA showed a bug (started at MESA 11.3), we talked to the MESA team that bug was eliminated after MESA 13.0. We are currently on MESA 17. This should not be reproducible anymore

Issue started with Stable Version 53, continued all the way through to the current Stable version that the Acer CB5-132T (R11) can use, 57 has not hit stable for this device yet.

Version 56.0.2924.110 (64-bit)
Platform 9000.91.0 (Official Build) stable-channel cyan
ARC Version 3756504
Firmware Google_Cyan.7287.57.100

It was visible, even more apparent in Beta Version 56 and 57 (few weeks ago), before I found the website, and mainly with WebGL-based sites and sometimes Youtube. Was less consistent than using the website though.

I apologise for my lack of technical information, I have no idea where to find such info.

#38:  What you provided is what I'm looking for.  Those version numbers show that you are indeed using an older build.

R57 should have MESA 13.1 which should have the fix for this bug. If you want a fix now you could try R57-BETA

What happened: 
Screen blacked out ~10 seconds while watching YouTube video. Tapped key board, flashed white the went back to normal, even continued playing video once it came back.

Running:
4 tabs (Pearson.com, Google Docs, PDF x2 & YouTube)
File Manager

MISC:
On battery (34%)
Head jack in use

Version 57.0.2987.146 (64-bit)
Platform 9202.64.0 (Official Build) stable-channel cyan
ARC Version 3880239
Firmware Google_Cyan.7287.57.100

Just had another one, see .txt file and look for gpu hang in the logs. Was watching youtube when it happened.

Deleted: apr17T09.46.59.txt 589 KB

apr17T09.46.59.txt 589 KB View Download

Still having issues with this on the latest Stable release. Version 57.0.2987.146 (64-bit) on an Acer R11.

Is this supposedly fixed? Because it sure doesn't seem like it. Would like an update on situation if possible.

Screen blacked out for ~10 seconds. Didn't respond to a tap on the keyboard. Eventually came back like nothing happened. I think it's from the music player, as that's when the black out occurred. I have over 300 songs on my SD card, and when I clicked one song, I think the default player is trying to load all the songs, and it just freezes and triggers the black out.

Submitted report.

Still seeing this on cyan. The screen doesn't go black anymore, but same GPU hang in logs.

Version 62.0.3202.97 Stable

(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.