CHECK failure: started in worker_thread.cc |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5736098708586496 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: CHECK failure Crash Address: Crash State: started in worker_thread.cc blink::scheduler::WorkerThread::WorkerThread blink::Thread::CreateThread Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=601948:601961 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5736098708586496 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 25
With reference to the Issue 898345 , assigning it to yutak@ for further triage
,
Oct 25
This test simply creates too many threads and hits the system limit. The CHECK failure is intentional, so WAI.
,
Nov 1
ClusterFuzz testcase 5736098708586496 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Nov 1
,
Nov 1
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by gwa...@gmail.com
, Oct 25