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

Issue 762364 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: r. Sending zygote magic failed in zygote_linux.cc

Project Member Reported by ClusterFuzz, Sep 6 2017

Issue description

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

Fuzzer: bj_broddelwerk
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  r. Sending zygote magic failed in zygote_linux.cc
  content::Zygote::ProcessRequests
  content::ZygoteMain
  
Sanitizer: address (ASAN)

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

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: msrchandra@chromium.org
Labels: Test-Predator-Correct-CLs
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to the concern owner from Predator results --
Regression information is not available. The result is the blame information. 

Author: rch@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/82d89abc03ea6fd6b9258f0e57be0290b33d7eb1
Time: Fri Feb 28 18:25:34 2014
The CL last changed line 791 of file logging.cc, which is stack frame 1. 

Author: brettw@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/b75346c61152a822fa38b1a1436581a549203a46
Time: Sun May 13 03:48:38 2012
The CL last changed line 142 of file zygote_linux.cc, which is stack frame 2. 

Author: agl@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/cc8f146d34a3b13cd80d8b3530fd76445774b1c6
Time: Fri Jun 12 17:36:55 2009
The CL last changed line 574 of file zygote_main_linux.cc, which is stack frame 3. 

Author: dcheng
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f63a125013805bf3dd72f90ec33f4d0aa0606660
Time: Sat Dec 26 20:43:13 2015
The CL last changed line 324 of file content_main_runner.cc, which is stack frame 4. 

Author: marshall@chromium.org
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/f573ed6b419616e8d2ff7932d931be3c57105e14
Time: Fri Feb 10 15:58:52 2012
The CL last changed line 709 of file content_main_runner.cc, which is stack frame 5. 

Author: Ken Rockot
Project: chromium
Changelist: https://chromium.googlesource.com/chromium/src/+/74946c37525c8b29f9b7b117c2d092a31b467b4d
Time: Tue Apr 25 22:04:59 2017
The CL last changed line 469 of file main.cc, which is stack frame 6.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/74946c37525c8b29f9b7b117c2d092a31b467b4d

@rockot -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Cc: roc...@chromium.org
Owner: agl@chromium.org
I don't think my changes are relevant. Over to agl@ who refactored zygote support recently.
Project Member

Comment 3 by ClusterFuzz, Oct 1 2017

Components: Internals>Core Internals>Sandbox
Labels: Test-Predator-AutoComponents
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.

Comment 4 by agl@chromium.org, Oct 2 2017

Owner: ----
Status: Available (was: Assigned)
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Project Member

Comment 6 by ClusterFuzz, May 31 2018

Status: WontFix (was: Available)
ClusterFuzz testcase 5110363476721664 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