maxbogue@ could you please look into this.please feel free to re-assigned back if needed. thanks in advance !

This doesn't appear to have anything to do with sync.

yeah it doesn't appear anything so making this available

From the CL assigning to the concern owner,
https://chromium.googlesource.com/chromium/src/+log/d63fff7a531f19cfd18b2076a4ec419bd6be3ad1..f5a290136489fed2a16ead7552e4d5f8f9ed1f43?pretty=fuller

Suspected Commit# 046aebf318df29e149778a16b697364ab596e476
Suspected Review URL# https://codereview.chromium.org/2306633002

@perkj -- Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible assign it to the concern Dev.
Thank You.

Sorry for not updating. So according to the logs, threads can not be started. 
In my implementation this cause a Check. So I can remove that check just to get 
rid of the crash.

But obviously, if threads can't be started, whatever those threads were supposed to do will not work so I am sure about the value of that. 

I will try to reproduce and see what happens if I remove the Check. 

Is it possible to start by suppressing the error?  I think the code is doing the right thing by crashing on failing to create a thread (comparable to oom).

ClusterFuzz has detected this issue as fixed in range 420270:420294.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result in task_queue.cc
  rtc::TaskQueue::TaskQueue
  webrtc::internal::Call::Call
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=415934:416233
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=420270:420294

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94JO7pfbj0PtNDZGL4e163EytBzx00B8qh0WU6wpgGjkKV8-S8g4nY5qUlILbB4OtUHDKCVBqPME14xUGjFy0LiVevOxANRXXg0QrvmMlA1dCjUM0ox7XGf9HH7OIQvQ5HVrBn6NWLU3x06ZoJxHgoH3WzLOg?testcase_id=4506525815275520


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.

ClusterFuzz testcase is verified as fixed, closing issue.

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

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