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/+/efface138ceef999ffe0f82b1ac54281808c154f ([FileSystem] Use mojo sync calls to block worker threads).

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.

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

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

commit d909938c1000041dd64d3c29377dd3855d263078
Author: Adithya Srinivasan <adithyas@chromium.org>
Date: Thu Aug 30 13:53:45 2018

[FileSystem] Initialize base::File::Error variables with values

Bug:  878652 
Change-Id: Ibbf18905c3aad4160cb5476542504dc2ef30ba91
Reviewed-on: https://chromium-review.googlesource.com/1195795
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Adithya Srinivasan <adithyas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#587555}
[modify] https://crrev.com/d909938c1000041dd64d3c29377dd3855d263078/content/renderer/fileapi/file_system_dispatcher.cc

ClusterFuzz has detected this issue as fixed in range 587554:587555.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  content::FileSystemDispatcher::ReadDirectorySync
  content::WebFileSystemImpl::ReadDirectory
  blink::DOMFileSystemBase::ReadDirectory
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=585561:585562
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=587554:587555

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

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 4536553934946304 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