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

Issue 779616 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

logging_UserCrash failing on amd64-generic-asan

Project Member Reported by teravest@chromium.org, Oct 30 2017

Issue description

https://build.chromium.org/p/chromiumos/builders/amd64-generic-asan/builds/21753

/tmp/cbuildbot5GmJIe/smoke_suite/test_harness/all/SimpleTestVerify/1_autotest_tests/results-24-logging_UserCrash                                                 ERROR: Command </sbin/crash_reporter --init> failed, rc=1, Command returned non-zero exit status

We see this verified in /var/log/messages:
2017-10-30T09:01:16.483091-07:00 WARNING kernel: [    5.482437] init: crash-reporter main process (467) terminated with status 1

There is a leak detected for that pid:
https://00e9e64bacd545890a4b0fe9b19dea7cffd433de4928298f8a-apidata.googleusercontent.com/download/storage/v1/b/chromeos-image-archive/o/amd64-generic-asan%2FR64-10080.0.0-b21753%2Fvm_test_results_1%2Fsmoke_suite%2Ftest_harness%2Fall%2FSimpleTestVerify%2F1_autotest_tests%2Fresults-24-logging_UserCrash%2Flogging_UserCrash%2Fsysinfo%2Fvar%2Flog%2Fasan%2Fasan.467?qk=AD5uMEvEZGXmmKcEayI93ccxpYF3FZG9QNbN7mW-vcbCDXxsdIW7dMksRxrpOcxCLbHq3E2_WFuguQWPD_7I_0dO064VL_GH3FISFdHvE2DskD8N18kmPSaIVgbXqINuqMSBySJuvUAECciRIrZRMbdVynRVDRNGrk7nP7jFP5QzZ3gUA46TJyXLZUbdUy3sSoSBbOnsisUk8WWduNmPHq5rglG6kVz3JelMIOFc-gyCwVjkYiNBTS9QqWgMllbGBy39eg7SOmsLOlZLcwwm2RvDykxmNp6o1bphHrkopcIlSwGxGUAkJUPwoH6eRS5GucUFnU1laPcbnLG82FwNNH5ok7hdGAd5t1uU7KOy9Me5K7ElUf2QxeKQ1KtRrcM-idcpAxoPSj0DnyNWvo7SmoqodiFei_lCZXpeSMYLJPpRLciMwuijcsf77nDp94Fq0RP9vuCub3M5awPASrySHwSMCWt7amp3KDW-b8EelIeO9fozi-ZBKm6HoSF1l4NEAFgqWDkH9aTbWttnLc3mCHFBKMjZnyusQGM9WsHmuNRuGkYNi5URHb5oTSdDUPMeldgcvF_DXrOUVOC2I64G1WR81jgl12PHGg4ea_WF-Hb0dolOpaxjkhg_zYnTPe8XxMEIL0WN1BebY8c_JoBwBEpBZA22S7bXfIr5SAIccRXfJMtFfJkEVPWSWA2oHyiOXXSSqCCj7PDsR1IZq0rnDL1TDIzpG6NZkT931AzYeCi4JXSOdDy1cRBBi4b33DEmcBAsqFoq9tGte0Mk6SWBRP6d1rC_pSA5Lk4VYI5W7aOf5X-LFjV3NmEaLHig9G7cl0VKBDDVJFEEEDwJy2ke8Ei6yRXgy_yhRAQ3w0Xt1NwtAm-RVQLEyCiRjDwwbYVTQ7Oo2gLt_n7VW9WQcnX_6vvZg9zqLjfXmIfX9e2M8C6Nj6Vl0r60cvnzyPlIXOpLJZa9HG_e1IXXdEfbpty-gp5eXf04dJ1BvUifKESevK8YkJLORccAUpwf4mYMh3HU0ffGFdlah2Bycf6uptzUhqddT4p0jXwNVw

That would explain why we see this failure here and not on other builders. I haven't confirmed that yet, though.

Here are the leak contents:

=================================================================
==467==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 944 byte(s) in 1 object(s) allocated from:
    #0 0x59dc4741dbba  (/sbin/crash_reporter+0x137bba)
    #1 0x59dc4744d9d2  (/sbin/crash_reporter+0x1679d2)
    #2 0x7ecfe5d75735  (/lib64/libc.so.6+0x20735)
    #3 0x59dc4737dfa8  (/sbin/crash_reporter+0x97fa8)

Indirect leak of 56 byte(s) in 1 object(s) allocated from:
    #0 0x59dc4741dbba  (/sbin/crash_reporter+0x137bba)
    #1 0x7ecfe743c733  (/lib64/libminijail.so+0xa733)
    #2 0x59dc4744da19  (/sbin/crash_reporter+0x167a19)
    #3 0x7ecfe5d75735  (/lib64/libc.so.6+0x20735)
    #4 0x59dc4737dfa8  (/sbin/crash_reporter+0x97fa8)

Indirect leak of 9 byte(s) in 1 object(s) allocated from:
    #0 0x59dc47409d43  (/sbin/crash_reporter+0x123d43)
    #1 0x7ecfe743c74d  (/lib64/libminijail.so+0xa74d)
    #2 0x59dc4744da19  (/sbin/crash_reporter+0x167a19)
    #3 0x7ecfe5d75735  (/lib64/libc.so.6+0x20735)
    #4 0x59dc4737dfa8  (/sbin/crash_reporter+0x97fa8)

Indirect leak of 9 byte(s) in 1 object(s) allocated from:
    #0 0x59dc47409d43  (/sbin/crash_reporter+0x123d43)
    #1 0x7ecfe743c762  (/lib64/libminijail.so+0xa762)
    #2 0x59dc4744da19  (/sbin/crash_reporter+0x167a19)
    #3 0x7ecfe5d75735  (/lib64/libc.so.6+0x20735)
    #4 0x59dc4737dfa8  (/sbin/crash_reporter+0x97fa8)

Indirect leak of 1 byte(s) in 1 object(s) allocated from:
    #0 0x59dc47409d43  (/sbin/crash_reporter+0x123d43)
    #1 0x7ecfe743c778  (/lib64/libminijail.so+0xa778)
    #2 0x59dc4744da19  (/sbin/crash_reporter+0x167a19)
    #3 0x7ecfe5d75735  (/lib64/libc.so.6+0x20735)
    #4 0x59dc4737dfa8  (/sbin/crash_reporter+0x97fa8)

SUMMARY: AddressSanitizer: 1019 byte(s) leaked in 5 allocation(s).
 

Comment 1 by warx@chromium.org, Oct 30 2017

Cc: malaykeshav@chromium.org warx@chromium.org
Labels: Build-PFQ-Failures
saw it on amd64-generic-tot-asan-informational, so adding 'Build-PFQ-Failures' label

Comment 2 by warx@chromium.org, Oct 30 2017

Labels: -Build-PFQ-Failures
it will not block pfq, remove the label
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 31 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/0d9aea83673f921e92169788cbf73c7e61d7a44c

commit 0d9aea83673f921e92169788cbf73c7e61d7a44c
Author: Mike Frysinger <vapier@chromium.org>
Date: Tue Oct 31 06:21:28 2017

crash: free the minijail once we're done

BUG= chromium:779616 
TEST=precq passes

Change-Id: Ibeafe655e91209cc900627143882d9ed958a318b
Reviewed-on: https://chromium-review.googlesource.com/744501
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Justin TerAvest <teravest@chromium.org>
Reviewed-by: Justin Carlson <justincarlson@chromium.org>

[modify] https://crrev.com/0d9aea83673f921e92169788cbf73c7e61d7a44c/crash-reporter/crash_reporter.cc

Comment 4 by vapier@chromium.org, Oct 31 2017

Status: Fixed (was: Untriaged)

Comment 5 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 6 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)

Sign in to add a comment