CHECK failure: 0 == pthread_create(&thread_, &attr, &StartThread, this) in platform_thread.cc |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6145066564583424 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: CHECK failure Crash Address: Crash State: 0 == pthread_create(&thread_, &attr, &StartThread, this) in platform_thread.cc rtc::FatalMessage::~FatalMessage rtc::FatalMessage::~FatalMessage Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=mac_asan_chrome&range=470547:470564 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6145066564583424 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 28 2017
Predator and CL could not provide any possible suspects. Using Code Search for the file, "platform_thread.cc" assigning to the concern owner who worked on similar file. @kjellandar -- Could you please look into the issue, kindly re-assign if this is not related to your changes. Thank You.
,
Aug 28 2017
,
Aug 28 2017
This is working as intended. The thread can't be created because of ENOMEM (12, out of memory) and there's not much we can do in that situation.
,
Sep 4 2017
ClusterFuzz testcase 6145066564583424 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. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by tapted@chromium.org
, Aug 27 2017