Unable to find the exact suspect from the Regression range.

Assigning to noel@ for help in investigating this further.

I authored no change in the given range.  I suppose you are just to look for help to resolve.  I scanned the regression range change logs, didn't see anything obvious.

sigbjornf@, sorry to pass this on.  Could you please have a quick scan of the regression range and see if there is anything obvious / suspect?

No clear match seen either for this crash on creation of a compositor thread. I suspect the stack is the fallout from the actual problem, but what.. Have you discounted the skia commits as being the potential source?

Unable to find the exact suspect hence labelling accordingly.

> Have you discounted the skia commits as being the potential source?

No, but if you suspect it's Skia, then assign to skia person :)

ClusterFuzz has detected this issue as fixed in range 382185:382751.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5489377303592960

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

Crash Type: UNKNOWN
Crash Address: 0x000000000000
Crash State:
  base::CreateThread
  base::SimpleThread::Start
  content::RasterWorkerPool::Start
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=374908:374923
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=382185:382751

Minimized Testcase (0.62 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97QO4-joIMHxdlaU4_Lc8fbQUU_F2gCK8MRxSD5hPFcKMHX6gZ8Tx4ly_doX4R1FK_IUkVIHkIQ_O4f6x3XihlP6DjI4cxUDYb5hWYDNzMIKuvcOTLtWcAC6ZHXdf-5Nb9PDpoF3L33nMQfmxMusVJxVyyx0g

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Tagging as Fixed as per #6

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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