CHECK failure: len > 0 in zygote_linux.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6257692116254720 Fuzzer: markbrand_regex Job Type: linux_asan_content_shell_drt Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: len > 0 in zygote_linux.cc content::Zygote::ForkWithRealPid content::Zygote::ReadArgsAndFork Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6257692116254720 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. If the fix resolved the issue, please close the bug by marking as Fixed.
,
Aug 29 2017
Issue 760048 has been merged into this issue.
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Nov 7 2017
,
Nov 28 2017
ClusterFuzz testcase 5773159407288320 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by msrchandra@chromium.org
, Aug 29 2017Labels: Test-Predator-Wrong-CLs
Owner: tfarina@chromium.org
Status: Assigned (was: Untriaged)