+Leon, could you add a link to your feedback report?

Assigning to Hiro for prioritization.

Seems like a P0 if it's reproducible. Adding RBD label. +Josafat for visbility.

Just a note that this is on my lulu which is not officially supported. I
don't have another device to test on.

I submitted feedback at 10:25 this morning (UK) but can't see it in
https://www.google.com/tools/feedback/reports

*Leon Pritchard*
Technical Deployment Specialist
lpritchard@google.com | +44 20 3321 1831
[image: unnamed.gif]

Leon, could this be your report:

https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=66508905053

Unfortunately, it contains no logs.

I actually don't have access to that, if it is then we may have another bug that the "send feedback" within the Android Window isn't working correctly. I'm currently waiting for it to timeout again and I'll resubmit.

Just submitted feedback again from lpritchard@google.com. Checked screenshot and logs. Manually attached net-export and have a chromeOS debug log.

Sorry to bother you with this again, but could you submit one more feedback log, putting your e-mail address in the description? The reporter e-mail address gets redacted by the system, so I cannot search for it. If you put your e-mail in the description, I can find it.

I can't reproduce the problem in latest canary: 9731.0.0 / 61.0.3152.0, maybe it's fixed already.

Resubmitted with email in comments section

It looks to be handled at b/63136374

So, Samus 61.0.3144.0 / 9693.1.0 is indeed b/63136374 (manual Chrome uprev was a bad one)

Lulu 61.0.3136.5 / 9672.0.0 can be a different issue.

http://feedback/#/Report/68092374432

Zygote process is repeatedly crashing... Found the same issue reported by yoshiat@ on Samus b/62972024 but no updates there

07-11 12:05:40.689  3978  3978 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xffde5000 in tid 3978 (zygote)
07-11 12:05:40.742  4162  4162 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-11 12:05:40.742  4162  4162 F DEBUG   : Build fingerprint: 'google/samus/samus_cheets:7.1.1/R61-9672.0.0/4118168:user/release-keys'
07-11 12:05:40.742  4162  4162 F DEBUG   : Revision: '0'
07-11 12:05:40.742  4162  4162 F DEBUG   : ABI: 'x86'
07-11 12:05:40.742  4162  4162 F DEBUG   : pid: 3978, tid: 3978, name: zygote  >>> zygote <<<
07-11 12:05:40.742  4162  4162 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xffde5000
07-11 12:05:40.742  4162  4162 F DEBUG   :     eax 00000000  ebx 00000f8a  ecx 00000f8a  edx 0000000b
07-11 12:05:40.742  4162  4162 F DEBUG   :     esi f63bbb0c  edi f63bb9b0
07-11 12:05:40.742  4162  4162 F DEBUG   :     xcs 00000023  xds 0000002b  xes 0000002b  xfs 00000000  xss 0000002b
07-11 12:05:40.742  4162  4162 F DEBUG   :     eip f63bc430  ebp f63bba30  esp f63bb948  flags 00000296
07-11 12:05:40.744  4162  4162 F DEBUG   : 
07-11 12:05:40.744  4162  4162 F DEBUG   : backtrace:
07-11 12:05:46.203  4182  4182 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xff891000 in tid 4182 (zygote)

Found the bug for this one b/62885307

Summary:
* The failure in Samus 61.0.3144.0 / 9693.1.0 / 4123572 is b/63136374.
* The failure in Lulu 61.0.3136.5 / 9672.0.0 / 4118168 is Bug 735538.

Both looks to be fixed in more recent versions (9694.0.0 or after.)

This has been addressed/resolved.