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

Issue 686144 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug-Regression

Blocking:
issue 698865



Sign in to add a comment

Undefined-shift in decode_pitch_lag_low

Project Member Reported by ClusterFuzz, Jan 27 2017

Issue description

Labels: Test-Predator-Wrong M-56
Cc: nyerramilli@chromium.org
Labels: -Type-Bug Type-Bug-Regression
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)
Predator did not find any culprit.

Assigning to /src/media/OWNERS, requesting to check the issue and help.

note: Did not specific owner list for /src/media/filters/
Cc: hubbe@chromium.org
Probably from the recent ffmpeg roll, will take a look.
Labels: -OS-Linux OS-Chrome
ClusterFuzz builds the ChromeOS build of ffmpeg so it can fuzz all codecs, but we only ship AMR on ChromeOS.
Cc: dalecur...@chromium.org
Owner: tguilbert@chromium.org
=>tguilbert who's working on the next ffmpeg roll.
Seems to be fixed upstream as of 3 days ago.

https://github.com/FFmpeg/FFmpeg/commit/6bd79ba59f46a8b3133f28faae53b75540469803
Blocking: 698865
Project Member

Comment 8 by ClusterFuzz, Mar 16 2017

Labels: OS-Linux
Project Member

Comment 9 by ClusterFuzz, Mar 22 2017

ClusterFuzz has detected this issue as fixed in range 458516:458571.

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

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  decode_pitch_lag_low
  decode_pitch_vector
  amrwb_decode_frame
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=423338:423416
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=458516:458571

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95bjFsO9GKm6f668EF9ZLxlQcojYNiAlCZVJjsu7HXh5jjVnjtI_9Wxunu5OduWfDiZR7tlFCnwmzrN_oVWNGYyfPiiV19WUtWD64v6svAEMGbeQam-q_bDOjGyC28r1a1lGd_wxEps6F-oaibM52ml2J4xUPvRSicPdCltnj11Fll-TVkHZdCKPyEosGA6zVMw7D6JFpCpgCFYtkAqhJ7M8oC0SajEeBeQAfAtl6Eo28fZ5AENfMifbpIMFHi3huzT3cr0zNplm23Yv7ZYDDavCNGCUZMfvQaf12RAKnsyYF6MVXmTU5f14XRqhqSR0zSC5NWCZyGgcT7vkcHK4yvtDd3mIz_sRjMD6JqQRDXhOEDBI5s?testcase_id=5577211064352768


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

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

Comment 10 by ClusterFuzz, Mar 22 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5577211064352768 is verified as fixed, so closing issue.

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

Sign in to add a comment