Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3f921557c4cb83453bfce0fe8637e489a90064ad (Drop UseCounter usage measurement on view-source pages.).

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.

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

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

Did bisect on asan-linux-debug.
Found good on asan-linux-debug-475503
Found bad on asan-linux-bebug-475519
Did a code search on https://chromium.googlesource.com/chromium/src/+log/e11116938aaefd39902c8441f25bd3e230e9c487
Seems like the only thing that touched Media related code was this:
https://chromium.googlesource.com/chromium/src/+/da1ebb6c4b424e74296c55b180055d1a98b73832

hiroshige@chromium.org, could you please take a look into this issue?

Thanks

ClusterFuzz has detected this issue as fixed in range 563960:563961.

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

Fuzzer: marty_html_twiddler
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !HasPendingActivity() in HTMLMediaElement.cpp
  blink::HTMLMediaElement::ContextDestroyed
  blink::HTMLVideoElement::ContextDestroyed
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=523893:523905
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=563960:563961

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

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 5086057272705024 is verified as fixed, so closing issue as verified.

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