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

Issue 646190 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Chrome crash reports are missing source filenames in crash reports.

Project Member Reported by son...@google.com, Sep 12 2016

Issue description

Version: 8743.23.0
OS: ChromeOS

What steps will reproduce the problem?
(1) Sign in to the device.
(2) Trigger chrome crash.
     "about:crash"
            or
     "about:inducebrowsercrashforrealz"
 
(3) Click on "start uploading crashes" link on chrome://crashes page.
(4) Check the crash report on server with crash ID.

What is the expected output?
Crash report should contain source filenames.


What do you see instead?
Chrome crash reports are missing source filenames in crash reports.

Crash report links:
https://crash.corp.google.com/browse?stbtiq=c552f17500000000
https://crash.corp.google.com/browse?stbtiq=02f34d9500000000

https://screenshot.googleplex.com/qCE8b7eQsz7


Please use labels and text to provide additional information.
Good crash report: https://crash.corp.google.com/browse?stbtiq=c5af897500000000
 

Comment 1 by vapier@chromium.org, Sep 13 2016

Mergedinto: 641188
Status: Duplicate (was: Untriaged)
Labels: M-53
Status: Untriaged (was: Duplicate)
Summary: Chrome crash reports are missing source filenames in crash reports. (was: [Big,Pit] Chrome crash reports are missing source filenames in crash reports.)
Source filename still can't loaded in ChromeOS build 8530.96.0 / 53.0.2785.154. 

https://crash.corp.google.com/browse?stbtiq=a21ff21d00000000#4
https://crash.corp.google.com/browse?stbtiq=e8180a1d00000000#4 

Let's re-open this bug as the issue 641188 seems different and marked as fixed. 
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 7 2016

Labels: Hotlist-Google

Sign in to add a comment