Assigning to concern owner from Predator results --
Regression information is not available. The result is the blame information. 

Author: brettw@google.com
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/d028296ec1c0fdfbd40e2390ca3121de7055295d
Time: Sat Jan 01 16:08:52 2011
The CL last changed line 18 of file debugger_win.cc, which is stack frame 0. 

Author: rch@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/82d89abc03ea6fd6b9258f0e57be0290b33d7eb1
Time: Fri Feb 28 18:25:34 2014
The CL last changed line 784 of file logging.cc, which is stack frame 1. 

Author: hclam
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/5a5ee680f9fc9647e3b7228d181fc7e2bb7ddecf
Time: Thu Feb 05 04:18:22 2015
The CL last changed line 842 of file udp_socket_win.cc, which is stack frame 2. 

Author: hclam
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/5a5ee680f9fc9647e3b7228d181fc7e2bb7ddecf
Time: Thu Feb 05 04:18:22 2015
The CL last changed line 391 of file udp_socket_win.cc, which is stack frame 3. 

Author: xjz
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/74f752173cf8084d9f96073eaa88236f0ac54b79
Time: Wed Feb 24 00:20:17 2016
The CL last changed line 178 of file udp_transport.cc, which is stack frame 4. 

Author: tzik
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/99de02ba952b0a69291f81c5b8ca14d81cc1f74f
Time: Fri Jul 01 05:54:12 2016
The CL last changed line 329 of file bind_internal.h, which is stack frame 5. 

Author: ajwong
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/4f13f74b94d6f0a39b73a832217c5ccc2f02e60f
Time: Thu Feb 09 23:52:40 2017
The CL last changed line 57 of file task_annotator.cc, which is stack frame 6.

Assigning to one of the reviewers how worked on the file.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/5a5ee680f9fc9647e3b7228d181fc7e2bb7ddecf

@rch -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Ok, this is getting a bit frustrating. A couple times a week, I get one of these bugs assigned to me because I touched the logging code back in *2014*. This is never going to be the root cause of any of the crashes.

Anyway, bouncing to msrchandra@chromium.org

ClusterFuzz has detected this issue as fixed in range 495542:495573.

Detailed report: https://clusterfuzz.com/testcase?key=5374523812872192

Fuzzer: ipc_fuzzer_gen
Job Type: windows_asan_chrome_ipc
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  (SOCKET)(~0) != socket_ in udp_socket_win.cc
  net::UDPSocketWin::InternalRecvFromNonBlocking
  net::UDPSocketWin::RecvFrom
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_ipc&range=495542:495573

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5374523812872192

See https://github.com/google/clusterfuzz-tools for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5374523812872192 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.