Assigning to concern owner from Predator results --
The result is a list of CLs that change the crashed files. 

Author: nisse
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/c0ff88b15124baa1dbcd671f4b7f8ffeba5b7144
Time: Fri May 05 09:23:02 2017
File peerconnectionfactory.cc is changed in this cl (and is part of stack frame #8, "webrtc::PeerConnectionFactory::CreatePeerConnection")
Minimum distance from crash line to modified line: 64. (file: peerconnectionfactory.cc, crashed on: 302, modified: 366).


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

ClusterFuzz has detected this issue as fixed in range 485789:485825.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: mac_asan_chrome
Platform Id: mac

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0 == pthread_create(&thread_, &attr, &StartThread, this) in platform_thread.cc
  rtc::FatalMessage::~FatalMessage
  rtc::FatalMessage::~FatalMessage
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=470547:470564
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=485789:485825

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 4938420517601280 is verified as fixed, so closing issue.

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