Issue metadata
Sign in to add a comment
|
Crash symbolization for ChromeOS ARM builds regressed significantly, late in M55 |
||||||||||||||||||||||
Issue descriptionChrome Version: 55.0.2883.0+ OS: ChromeOS What steps will reproduce the problem? (1) Crash a tab (or the browser) on an ARM device. (2) Use chrome://crashes to get the corresponding crash-upload Id. (3) Look up the crash. What is the expected result? Expect that crashes are beautifully symbolized. What happens instead? Most of the time: Symbols, there are few. Bug diagnosis, it is impaired. Specifically the crashes appear to be lacking information on the chrome binary itself, with missing debug name and debug ID fields.
,
Feb 14 2017
I'm guessing you wanted mmentovai not mmenke. tobaisjs has been working on Breakpad ARM, but mostly for Android.
,
Feb 14 2017
Tobias or Joshua, do you have any ideas?
,
Feb 14 2017
This is happening because the CFI data is stripped from the breakpad symbol files. I asked ChromeOS folks to bump up the symbol file size limit to 700 MB (from 500 MB). I'm also deploying a server side change to support the bigger size. For more details: https://b.corp.google.com/issues/30860471
,
Feb 25 2017
Re #4: When will the fix make it at least to CrOS dev-channel?
,
Feb 27 2017
the fix landed a week ago, so it should be in the latest builds for M56 and newer. TPMs declined M55 merge because there aren't going to be any new M55 builds and the focus is on newer stuff.
,
Oct 9
i assume this is resolved at this point |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by w...@chromium.org
, Feb 13 2017