New issue
Advanced search Search tips

Issue 646914 link

Starred by 1 user
Status: Untriaged
Merged: issue 647498
Owner: ----
Cc:
mark@chromium.org
scottmg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

hang, and no crash report on Linux

Project Member Reported by wfh@chromium.org, Sep 14 2016 
Version: 53.0.2785.113 (Official Build) (64-bit)
OS: Ubuntu 14.04 LTS trusty 3.13.0-83-generic x86_64

What steps will reproduce the problem?
(1) Visit https://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?prefix=Linux_x64/
(2) Type in some numbers in top left "filter"
(3) Edit the filter a bit, wait a bit, wait for a hang?

What is the expected output?

not hang. also, when I click 'Kill' on the hang message, I should generate a crash report.

What do you see instead?

Tab hung, and when I clicked Kill, I got no crash report.

Please use labels and text to provide additional information.

Comment 1 by wfh@chromium.org, Sep 14 2016

Cc: mark@chromium.org scottmg@chromium.org
Actually I typed '417' into the Filter box at the top, then waited a bit. changed it to '17' then waited a little bit... then the hung renderer dialog appeared.

The part I find most worrying here is that no crash report is generated.
417_crash.png
186 KB View Download

Comment 2 by wfh@chromium.org, Sep 14 2016 

I get an entry in the RENDERER_UNRESPONSIVE_IN_FLIGHT_EVENTS (1) bucket for ChildProcess.HangRendererType while it's hanging.

After clicking 'Kill' I get an entry in RENDERER_TYPE_RENDERER bucket for BrowserRenderProcessHost.ChildKills after termination.

I'm also getting entries in Tabs.SadTab.KillCreated for the sad tab, which is good.

Just, no crash report.

Comment 3 by wfh@chromium.org, Sep 14 2016 

also, stability.renderer_hang_count is incrementing, which is also good.

Comment 4 by wfh@chromium.org, Sep 14 2016 

stability.breakpad_registration_fail is 1 which is worrying...? or not?

https://uma.googleplex.com/p/chrome/timeline_v2?sid=ac57c133d5b313f0ff54fe3f5746425a shows maybe 10% of users have breakpad registration failure, whatever that means.

Comment 5 by wfh@chromium.org, Sep 23 2016

Mergedinto: 647498
Status: Duplicate (was: Untriaged)

Comment 6 by wfh@chromium.org, Sep 23 2016

Status: Untriaged (was: Duplicate)

Comment 7 by wfh@chromium.org, Sep 23 2016

Summary: hang, and no crash report on Linux (was: hang, and no crash report)
I can get a crash from a chrome://hang tab, so something is strangely wrong here. Perhaps I will try and simulate a hang inside v8, or perhaps this was Linux only.
►

Sign in to add a comment