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/+/c39707c16e37d03a3e3ae79d297172fdaf68f4c7 (Plumb stop loading signal to ResourceLoadScheduler.).

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 issue seems unrelated to the referenced CL.

@panicker: Please set to Untriaged next time, so we see this in our triaging queue.

Ulan, this seems to be a race on IncrementalMarkingJob::task_pending_. Can you take a look please?

ClusterFuzz has detected this issue as fixed in range 606653:606661.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Data race READ 1
Crash Address: 0x7b2800040292
Crash State:
  v8::internal::IncrementalMarkingJob::ScheduleTask
  v8::internal::Isolate::SetRAILMode
  v8::Isolate::SetRAILMode
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=523888:523922
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=606653:606661

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

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

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