CHECK failure: bitrate_bps >= 0 in video_bitrate_allocation.cc |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4865295336079360 Fuzzer: mojo_fuzzer Job Type: linux_asan_chrome_mojo Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: bitrate_bps >= 0 in video_bitrate_allocation.cc media::VideoBitrateAllocation::SetBitrate mojo::StructTraits<media::mojom::VideoBitrateAllocationDataView, media::VideoBit Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=585999:586001 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4865295336079360 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Dec 22
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/8a3fad5140069b8ae038d5224b52b62756f0bbbb (reland: window-service: moves most mojoms to ws namespace). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Jan 7
My patch just changed namespaces. Passing to sprang@ as it looks like he wrote these tests. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 22Labels: Test-Predator-Auto-Components