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 adding ccs based on suspected regression changelists:

Fix typo (Defautl -> Default). by nick@chromium.org - https://chromium.googlesource.com/chromium/src/+/f5443e092d1303656080785099b87e9124f6268e

Support jumbo builds in platform/wtf (-2 CPU minutes) by bratell@opera.com - https://chromium.googlesource.com/chromium/src/+/a2746bc31443102369bea08eb3cbb06de91a053b

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Both suspects look unlikely. The typo change is just a rename of symbols (though that might have changed some stack trace) and jumbo is not enabled so there should be no change in normal builds.

Adding Test-Predator-Wrong-CLs to get a second opinion.

Unable to find the suspect through code search and also from the available regression range, hence cc'ing to @dcheng for more updates on this issue who have worked on similar  issue 770122  earlier.

@dcheng- Could you please take a look in to this issue?

Thanks!

My guess is this is throwing an exception which generates a very long error message. I don't really feel like it's worth doing anything here: a renderer can OOM itself pretty easily in any number of ways.

Agreed.  "Array(248414443).join()" is too huge, and a CHECK failure at PartitionAlloc is expected.

ClusterFuzz has detected this issue as fixed in range 538633:538638.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  p in pickle.cc
  [vdso]
  base::Pickle::Resize
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=508795:508884
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=538633:538638

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

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.

 Issue 823105  has been merged into this issue.

 Issue 825526  has been merged into this issue.

 Issue 832241  has been merged into this issue.