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

Issue 791868 link

Starred by 1 user
Status: Duplicate
Owner: ----
Closed: Dec 2017
Cc:
█ ivanpe@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Crashes from ChromeOS kevin are not symbolized

Project Member Reported by w...@chromium.org, Dec 5 2017 
Chrome Version: 64.0.3280.5 (Official Build) dev (32-bit)
OS: ChromeOS

Crash reports c8bc4b59d4202f3a and 80b9e72d2e3310b6, for example, have stack traces with no symbols.

Comment 1 by w...@chromium.org, Dec 5 2017 

Strangely, some earlier crashes from the same device & version are symbolized (e.g. report 1e7d120d32d53bd5).

Comment 2 by kbleicher@google.com, Dec 7 2017 

M64 beta is targeted for next Tuesday (12-Dec); anything we can do to close this out and/or retag as stable block is appreciated.  Can we triage and assign ASAP? Thanks!

Comment 3 by kbleicher@google.com, Dec 7 2017 

Pinged Ivan to take a look per pending Beta next week.

Comment 4 by ivanpe@chromium.org, Dec 7 2017

Mergedinto: 779840
Status: Duplicate (was: Untriaged)
This is a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=779840:

The debug identifier for chrome is 0:

Start	End	Module	Version	Debug Identifier	
0x0de00000	0x116e6000	/opt/google/chrome/chrome		000000000000000000000000000000000

We expect this to be fixed in Crashpad.  The Crashpad client for Android and Linux is almost ready.  The Crashpad client for ChromeOS is expected in Q1-Q2 2018.

Comment 5 by ivanpe@chromium.org, Dec 9 2017

Mergedinto: -779840 793452
Scratch my previous comment.  This is likely a duplicate of 793452.
►

Sign in to add a comment