Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/ffb5de3934abd4e16399b2f79e7100823c6076fd (Don't propagate cmdline flags that are not read by renderer processes.).

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.

+media ux team folks since that was the cause last time.

inferno@, can you please 1) route this bug to a better owner and 2) help ensure that predator does a better job of picking an owner?  As in all the other cases, the CL blamed by the predator is unlikely to be the culprit - see all the bugs here:
https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ATest-Predator-Wrong-CLs+commentby%3Alukasza%40chromium.org+ffb5de3934abd4e16399b2f79e7100823c6076fd&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

Issue 846219 has been merged into this issue.

@mlamouri, did you mean to assign this to you or someone on your team? I still suspect this is related to recent UX changes.

I have a CL ready to land that simply remove this DCHECK.

Hmm, make sure you explain why that's okay in your CL :)

ClusterFuzz has detected this issue as fixed in range 568505:568507.

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

Fuzzer: inferno_flicker
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  has_audio || has_video in media_web_contents_observer.cc
  content::MediaWebContentsObserver::OnMediaPlaying
  void IPC::DispatchToMethodImpl<content::MediaWebContentsObserver, void
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=529050:529051
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=568505:568507

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

See https://github.com/google/clusterfuzz-tools 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 5253714059984896 is verified as fixed, so closing issue as verified.

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