New issue
Advanced search Search tips

Issue 767506 link

Starred by 4 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug

Blocked on:
issue 725605
issue 736675
issue 740044
issue 744734
issue 750267
issue 754946



Sign in to add a comment

Meta bug: a memory corruption on Android starting in June.

Project Member Reported by yzshen@chromium.org, Sep 21 2017

Issue description

We started seeing a memory corruption issue on Android around the middle of June. (According to crbug.com/736675, it was first seen in 61.0.3130.3.)

With this issue, small allocations got corrupted, for example, we were consistently seeing std::map with values of type scoped_refptr<T> being nulled out.

This is a meta bug keeping track of all bug reports sharing the same root cause.
 

Comment 1 by yzshen@chromium.org, Sep 21 2017

Labels: -Pri-3 Pri-1

Comment 2 by yzshen@chromium.org, Sep 21 2017

Blockedon: 736675

Comment 3 by yzshen@chromium.org, Sep 21 2017

Blockedon: 744734

Comment 4 by yzshen@chromium.org, Sep 21 2017

Blockedon: 750267 754946 740044 725605

Comment 5 by roc...@chromium.org, Sep 21 2017

It's worth noting that although bug 736675 pegs 61.0.3130.3 as the earliest revision with such crashes, we had previously pegged 61.0.3143.0 based on our own symptomatic crashes.

We should therefore be mindful of the fact that the trampler could have been introduced before the 3129-3130 range.
Something in 61.0.3130.3 definitely tickled things such that it started affecting the histograms subsystem, though - as all the histograms related crashes started appearing only as of that build.
Cc: yhirano@chromium.org
Labels: Stability-Memory

Sign in to add a comment