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/+/bea6537a032fb89f8f3fd6ee839267f9963fddfe (Change SMILTimeContainer::scheduled_animations_ to use ephemeron).

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.

Reverting in https://chromium-review.googlesource.com/c/chromium/src/+/1176401. This caused a dozen bugs with different stacks.

ClusterFuzz has detected this issue as fixed in range 583246:583247.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x0f5b5ef16b08
Crash State:
  blink::SMILTimeContainer::SetElapsed
  setCurrentTimeMethod
  blink::V8SVGSVGElement::setCurrentTimeMethodCallback
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=583155:583156
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=583246:583247

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

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

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot