New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 768115 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS || error

Project Member Reported by ClusterFuzz, Sep 23 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=6630080389578752

Fuzzer: marty_html_twiddler
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  error == EPERM || error == EUSERS || error == EINVAL || error == ENOSYS || error
  logging::ErrnoLogMessage::~ErrnoLogMessage
  sandbox::Credentials::CanCreateProcessInNewUserNS
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6630080389578752

Additional requirements: Requires Gestures

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. We will auto-close the bug if the crash is not seen for 14 days.
 
Cc: jln@chromium.org
Owner: thomasanderson@chromium.org
Status: Started (was: Untriaged)
Cc: infe...@chromium.org
Labels: ClusterFuzz-Ignore
Status: WontFix (was: Started)
Closing this issue since it's caused by running out of memory

Sign in to add a comment