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

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

Based on the blame range, it looks that a likely candidate is r612820 by beccahughes, which introduced AudioFocusWebContentsObserver (appearing on the stack).

I have a CL out to fix

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/32fd6188bc344a693d19370069e919e96607e38d

commit 32fd6188bc344a693d19370069e919e96607e38d
Author: Becca Hughes <beccahughes@chromium.org>
Date: Wed Dec 05 18:30:27 2018

[Audio Focus] Fix crash in AFWCO

Fix crash in AudioFocusWebContentsObserver.

BUG=911006, 910936 

Change-Id: I6789413b0356ab867f7e88b0815023f296603a96
Reviewed-on: https://chromium-review.googlesource.com/c/1361446
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#614035}
[modify] https://crrev.com/32fd6188bc344a693d19370069e919e96607e38d/chrome/browser/apps/platform_apps/audio_focus_web_contents_observer.cc

ClusterFuzz has detected this issue as fixed in range 614034:614040.

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

Fuzzer: noel-image-surku
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000078
Crash State:
  content::WebContentsImpl::DidFinishNavigation
  content::NavigationHandleImpl::~NavigationHandleImpl
  content::NavigationHandleImpl::~NavigationHandleImpl
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=612813:612825
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=614034:614040

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

Additional requirements: Requires Gestures

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

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