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

Issue 672513 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 672427
Owner: ----
Closed: Dec 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Spike in various '`anonymous namespace'' dealloc/calloc/malloc related crashes on the latest Mac canary(57.0.2945.3)

Project Member Reported by ajha@chromium.org, Dec 8 2016

Issue description

Few of the top magic signatures that have shown spike on Mac canary(57.0.2945.3):


1. `anonymous namespace'::ZombieDealloc' . Link to list of the builds: https://goto.google.com/viqpt
2. base::`anonymous namespace'::oom_killer_malloc . Link to the list of the builds: https://goto.google.com/evxsf
3. base::`anonymous namespace'::oom_killer_calloc . Link to the list of the builds: https://goto.google.com/ozbif


Considering below as the changelog:
====================================
https://chromium.googlesource.com/chromium/src/+log/57.0.2944.0..57.0.2945.0?pretty=fuller&n=10000

Nothing from the above range looks related.

Looping stability sheriff for help in further investigation of this. Marking this as Dev blocker due to spike from the last canary. Feel free to adjust if this should not be blocking.
 

Comment 1 by ajha@chromium.org, Dec 8 2016

Labels: Needs-triage
Cc: mmand...@chromium.org
mmandlis@, could you please check all the above Mac renderer crashes are valid?

Appreciate your help!
Could you, please, clarify what you mean by "valid crashes"?
Looking at the magic signatures, there is a warning on the stack trace quality.
Cc: ivanpe@chromium.org
I meant to say, we do not see proper symbolization in the crash stack. Ex: go/crash/7b56c56300000000

Shall we log a different bug to track them?

Thank you!
This report has missing symbols file, can you please, try uploading it?
If needed, we may manually resubmit this report after the symbols file is uploaded. Thanks!
I am not very sure, how i can upload the symbols file. Moreover i didn't see this crash on my machine, just shared the above example from go/chromecrash.

Thank you!
The symbols files are uploaded as part of the build process, maybe smth failed during the build.
Many of the crashes from 57.0.2945.3 are basically variants of  issue 672427  (you can see the same stack on thread 0).
Mergedinto: 672427
Status: Duplicate (was: Untriaged)
Project Member

Comment 10 by bugdroid1@chromium.org, Dec 12 2016

Project Member

Comment 11 by bugdroid1@chromium.org, Dec 12 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/b648ed53023e7332cfe1804584d6a99ac12bf32c

commit b648ed53023e7332cfe1804584d6a99ac12bf32c
Author: Steven Bennetts <stevenjb@chromium.org>
Date: Mon Dec 12 22:45:09 2016

Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1211172, build_number 3718

Marking set of ebuilds as stable

amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

daisy-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

amd64-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST

"Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-57.0.2949.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-57.0.2949.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-57.0.2949.0_rc-r1.afdo'} and updated Manifest"

Marking latest_release for chromium-source ebuild with version 57.0.2949.0 as stable.

Marking latest_release for chromeos-chrome ebuild with version 57.0.2949.0 as stable.

BUG= chromium:672513 
TEST=None
CQ-DEPEND=*I60fff5d25f85ddc0900ffc5bdcaf4cec74d5df9a

Change-Id: Ic486fa4b6c136448db49a505f10dbbed7230f296
Reviewed-on: https://chromium-review.googlesource.com/419116
Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org>
Tested-by: Steven Bennetts <stevenjb@chromium.org>

[rename] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos-base/chromeos-chrome/chromeos-chrome-57.0.2949.0_rc-r1.ebuild
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[rename] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos-base/chromium-source/chromium-source-57.0.2949.0_rc-r1.ebuild
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos-base/chromeos-chrome/Manifest
[modify] https://crrev.com/b648ed53023e7332cfe1804584d6a99ac12bf32c/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf

Sign in to add a comment