[Google Pixel 2 Questions & Answers] eanema:
Hi All,

I have recently (as in the past three or four days) have noticed my pixel 2 is crashing. I will be in the middle of anything really - watching a youtube video, last time I was preparing to log into a skype meeting... first the screen brightness increases to maximum and the system in unresponsive, then a moment later I am kicked out to the lock screen and I will need to re-enter my password (instead of just fingerprint scanning) because it thinks I have just power cycled my phone. I downloaded the logcat and had a look through it:

~/Desktop$ adb logcat > logcat.txt
^C
~/Desktop$ grep "Build fingerprint" logcat.txt
12-09 09:53:19.394 4247 4247 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 11:43:20.845 17233 17233 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 13:30:49.843 27809 27809 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 15:16:55.320 6546 6546 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 16:20:28.016 16032 16032 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 17:52:01.305 27423 27423 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 18:15:46.459 4530 4530 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 21:01:27.411 19212 19212 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 22:08:47.234 29161 29161 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-09 23:25:52.732 5523 5523 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 00:38:09.041 16731 16731 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 10:57:36.963 16230 16230 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 11:34:07.681 32519 32519 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 12:53:14.116 17878 17878 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 15:59:41.529 4502 4502 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'

There was 15 crash reports, all of them looking *very* similar to this one:

12-10 12:53:14.021 32534 17875 F libc : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x702df0eaea in tid 17875 (netd), pid 32534 (Binder:32534_2)
12-10 12:53:14.116 17878 17878 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-10 12:53:14.116 17878 17878 F DEBUG : Build fingerprint: 'google/walleye/walleye:9/PQ1A.181105.017.A1/5081125:user/release-keys'
12-10 12:53:14.116 17878 17878 F DEBUG : Revision: 'MP1'
12-10 12:53:14.116 17878 17878 F DEBUG : ABI: 'arm64'
12-10 12:53:14.116 17878 17878 F DEBUG : pid: 32534, tid: 17875, name: netd >>> /system/bin/netd <<<
12-10 12:53:14.116 17878 17878 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x702df0eaea
12-10 12:53:14.116 17878 17878 F DEBUG : x0 000000702e873904 x1 000000702df0eaea x2 000000000000007e x3 000000702e873900
12-10 12:53:14.116 17878 17878 F DEBUG : x4 000000702df0eb68 x5 000000702e873982 x6 0000000000000000 x7 0000000000000000
12-10 12:53:14.116 17878 17878 F DEBUG : x8 000000702df0eb68 x9 0000000000000004 x10 000000702e873900 x11 00000000ffffffff
12-10 12:53:14.116 17878 17878 F DEBUG : x12 000000702f594418 x13 0000000000000000 x14 000000702f400000 x15 0000000000000000
12-10 12:53:14.116 17878 17878 F DEBUG : x16 000000646dc47420 x17 00000070afae1b70 x18 00000070afbbf000 x19 000000702e830180
12-10 12:53:14.116 17878 17878 F DEBUG : x20 000000702de133f8 x21 000000702e873900 x22 000000702de13588 x23 000000702df0eb68
12-10 12:53:14.116 17878 17878 F DEBUG : x24 000000702df0eaea x25 0000000000000005 x26 000000702df11588 x27 000000646dc14930
12-10 12:53:14.116 17878 17878 F DEBUG : x28 000000702e80fdc0 x29 000000702de133d0
12-10 12:53:14.116 17878 17878 F DEBUG : sp 000000702de13380 lr 000000646dc14564 pc 00000070afae1c58
12-10 12:53:14.132 17878 17878 F DEBUG :
12-10 12:53:14.132 17878 17878 F DEBUG : backtrace:
12-10 12:53:14.132 17878 17878 F DEBUG : #00 pc 000000000001dc58 /system/lib64/libc.so (memcpy+232)
12-10 12:53:14.132 17878 17878 F DEBUG : #01 pc 000000000006c560 /system/bin/netd (android::net::DnsTlsSocket::sendQuery(android::net::DnsTlsSocket::Query const&)+192)
12-10 12:53:14.133 17878 17878 F DEBUG : #02 pc 000000000006c0fc /system/bin/netd (android::net::DnsTlsSocket::loop()+308)
12-10 12:53:14.133 17878 17878 F DEBUG : #03 pc 000000000006c96c /system/bin/netd
12-10 12:53:14.133 17878 17878 F DEBUG : #04 pc 0000000000083114 /system/lib64/libc.so (__pthread_start(void*)+36)
12-10 12:53:14.133 17878 17878 F DEBUG : #05 pc 00000000000233bc /system/lib64/libc.so (__start_thread+68)

Looking at this I see that all of the backtraces end at libc.so (in memcpy). I assume that the crash is actually in /system/bin/netd because it seems much more likely than an crash originating in libc... I do have all my apps/updates installed/up to date and this is a new issue for me. I have had this phone for over a year now and have not had any issues such as this in the past...

I am wondering if anyone has seen this problem before? Solutions? Is this a new bug that may have come in a recent system update?

Thanks for your attention