New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 884450 link

Starred by 1 user
Status: Assigned
Owner:
█ philipel@chromium.org
Last visit > 30 days ago
Cc:
jonasolsson@chromium.org
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in rtc::webrtc_checks_impl::FatalLog

Project Member Reported by ClusterFuzz, Sep 15 
Detailed report: https://clusterfuzz.com/testcase?key=6694741822144512

Fuzzer: libFuzzer_rtp_frame_reference_finder_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900003f5d
Crash State:
  rtc::webrtc_checks_impl::FatalLog
  Call<>
  webrtc::video_coding::RtpFrameObject::RtpFrameObject
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=591176:591178

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Sep 15

Cc: philipel@webrtc.org
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Added is_last_packet_in_frame to match is_first_packet_in_frame. by philipel@webrtc.org - https://webrtc.googlesource.com/src/+/ef615ea7a3960f13aeb341e9a76e627aff875238

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 2 by dtapu...@chromium.org, Sep 18

Components: Blink>WebRTC

Comment 3 by kkaluri@chromium.org, Sep 19

Cc: kkaluri@chromium.org
Labels: M-71 Test-Predator-Wrong
Owner: jonasolsson@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.

Using Code Search for the file, "rtc_base/checks.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://webrtc.googlesource.com/src.git/+/f8e5c110ee806992f4092220339939fe5c2d3cc9

jonasolsson@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

Comment 4 by kkaluri@chromium.org, Sep 19 

 Issue 884085  has been merged into this issue.

Comment 5 by jonasolsson@chromium.org, Sep 24

Cc: -philipel@webrtc.org jonasolsson@chromium.org
Owner: philipel@chromium.org
The fuzzers managed to trigger this check:
RTC_CHECK(last_packet->is_last_packet_in_frame).

@philipel: Does this look like a new bug introduced by your changes, or an old one just now being discovered?
Project Member

Comment 6 by ClusterFuzz, Oct 5

Labels: OS-Mac

Comment 7 by anatolid@chromium.org, Nov 19 

philipel@ are you looking into this?
Project Member

Comment 8 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6694741822144512 appears to be flaky, updating reproducibility label.

Comment 9 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

Comment 10 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
►

Sign in to add a comment