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

Issue 694940 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
█ ajwong@chromium.org
thestig@chromium.org
dpranke@chromium.org
█ pamg@google.com
scottmg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

failure to get crash dump observed on linux

Project Member Reported by jochen@chromium.org, Feb 22 2017 
on this try run: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/394078

I get failures like this: STDERR: [3045:3166:0221/034012.403892:2849592588:WARNING:crash_handler_host_linux.cc(325)] Could not translate tid, attempt = 1 retry ...

and no minidump. The content shell crash integration test on the same bot, however, runs successfully.

Comment 1 by jochen@chromium.org, Mar 20 2017

Cc: pamg@google.com dpranke@chromium.org thestig@chromium.org
Labels: -Pri-3 Pri-1
This continues to happen on bots. Given that they use the same system we use for regular crash reporting, this makes me wonder whether we're missing out on a significant fraction of minidumps from the wild.

e.g. https://storage.googleapis.com/chromium-layout-test-archives/linux_chromium_rel_ng/411739/layout-test-results/results.html

Comment 2 by dpranke@chromium.org, Mar 20 2017

Cc: ajwong@chromium.org scottmg@chromium.org

Comment 3 by thestig@chromium.org, Sep 13 2017

Status: WontFix (was: Untriaged)
Unless you see attempt = 3 often, I would not worry. Occasionally it takes a few tries.
►

Sign in to add a comment