Author: deadbeef
Component: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/516d53650db390902e12ba0b13e04462c085bbd6
Time: Wed Feb 24 01:24:52 2016
Lines 114-118 of file webrtcsessiondescriptionfactory.cc which potentially caused crash are changed in this cl (frame #0, "webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription").

Lines 825-831 of file webrtcsession.cc which potentially caused crash are changed in this cl (frame #1, "webrtc::WebRtcSession::SetRemoteDescription").

File peerconnection.cc is changed in this cl (and is part of stack frame #2, "webrtc::PeerConnection::SetRemoteDescription")
Minimum distance from crash line to modified line: 0. (file: webrtcsessiondescriptionfactory.cc, crashed on: 114, modified: 114).

@deadbeef: Request you to please take a look into it

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5708466095652864

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription
  webrtc::WebRtcSession::SetRemoteDescription
  webrtc::PeerConnection::SetRemoteDescription
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=377575:377601

Minimized Testcase (2.70 Kb): https://cluster-fuzz.appspot.com/download/AMIfv95_cNVva4awEn5EuzDjH8tPy1cYJ8FmLqmua5srZiPe9CmhsffKbLmgPbNZicq24bTNukUQSJhlCfB2UB11334Wov00htRTguuM1k2JSs1R0-kVM0AGbpeeyhRqP9jRc_z0i2SGsNeF1UZ_CTWDnaWGg1kt5g

Additional requirements: Requires HTTP

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.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5417570611494912

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription
  webrtc::WebRtcSession::SetRemoteDescription
  webrtc::PeerConnection::SetRemoteDescription
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=377575:377601

Minimized Testcase (15.65 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97jn8yY-hWnvQVQHBS76eHJ7uqQbOwOlzP6yzmawVhmK930ukNpwcKoJOFzxDRBaYv2A9DUTrUsBreQ3h2MOG33YLSjIHhgKCm0GvtQ51PqBa5Doz4FD8f2F4U_O5HFm1BM1I2Ee4oj7Y5Fae5juPH3P5HdaA

Additional requirements: Requires HTTP

Filer: ranjitkan

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5417570611494912

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription
  webrtc::WebRtcSession::SetRemoteDescription
  webrtc::PeerConnection::SetRemoteDescription
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=377575:377601

Minimized Testcase (15.65 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97jn8yY-hWnvQVQHBS76eHJ7uqQbOwOlzP6yzmawVhmK930ukNpwcKoJOFzxDRBaYv2A9DUTrUsBreQ3h2MOG33YLSjIHhgKCm0GvtQ51PqBa5Doz4FD8f2F4U_O5HFm1BM1I2Ee4oj7Y5Fae5juPH3P5HdaA

Additional requirements: Requires HTTP

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.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6425791367217152

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription
  webrtc::WebRtcSession::SetRemoteDescription
  webrtc::PeerConnection::SetRemoteDescription
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=377575:377601

Minimized Testcase (2.33 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94KpNh9OGU6yz8aHNwNG7vFLWFgd8uLc6cy41nmeEDxQZVyEE5Hr99jN7EX8Be31N5sV68ZytD4qFqqU2PLZTHXytU68jURIV4JK6kDYKhtrtx3inYg5vkF-rlY7-xi_uVs41lf6CS3A_ESlmyOxU1YGeM3sA

Additional requirements: Requires HTTP

Filer: ranjitkan

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

Fixed in https://codereview.webrtc.org/1754803002/; just waiting for a WebRTC roll.

ClusterFuzz has detected this testcase as flaky and is unable to reproduce it in the original crash revision. Skipping fixed testing check and marking it as potentially fixed.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6425791367217152

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  webrtc::WebRtcSessionDescriptionFactory::CopyCandidatesFromSessionDescription
  webrtc::WebRtcSession::SetRemoteDescription
  webrtc::PeerConnection::SetRemoteDescription
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=377575:377601

Minimized Testcase (2.33 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94KpNh9OGU6yz8aHNwNG7vFLWFgd8uLc6cy41nmeEDxQZVyEE5Hr99jN7EX8Be31N5sV68ZytD4qFqqU2PLZTHXytU68jURIV4JK6kDYKhtrtx3inYg5vkF-rlY7-xi_uVs41lf6CS3A_ESlmyOxU1YGeM3sA

Additional requirements: Requires HTTP

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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot