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

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

Predator and CL could not provide any possible suspects.
Using the code search for the file, “permission_service_impl.cc” assigning to concern owner from GIT revision log.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/4ead6c35d84fcb312402a0ad5984cb44021b524e

@raymes -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.
Thank You.

Pretty sure this is the same root cause as  issue 839197 

Actually duplicate of  issue 839194 

ClusterFuzz has detected this issue as fixed in range 557449:557450.

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

Fuzzer: mojo_fuzzer
Job Type: linux_asan_chrome_mojo
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  PermissionManager::RequestPermissions
  PermissionManager::RequestPermissions
  content::PermissionServiceImpl::RequestPermissions
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=555295:555297
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_mojo&range=557449:557450

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

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.