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

Issue 737780 link

Starred by 2 users
Status: Duplicate
Merged: issue 583730
Owner:
xiy...@chromium.org
Closed: Aug 2017
Cc:
█ rcui@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Crash that didn't generate a crash id

Project Member Reported by abodenha@chromium.org, Jun 28 2017 
Chrome Version: 60.0.3112.41 (Official Build) beta (64-bit)
OS: Chrome

See https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=abodenha&lReport=66792619691

What steps will reproduce the problem?
(1) Visit facebook.
(2) Scroll over a post that starts playing some video
(3) Keep scrolling

What is the expected result?
No boom

What happens instead?
Boom.


I'm unable to repro this, but I've had a few instances in the past week where a crash occurred and either didn't result in a crash id (even after clicking start upload and waiting) or where the only crash id points to a kernel warning that is supposedly benign (see crash/ee36182608000000)

This time I immediately filed feedback in the hopes of grabbing some useful data.

xiyuan@ can you take a look at the logs and see if anything stands out?

Comment 1 by xiy...@chromium.org, Jun 29 2017 

The log has a chrome crash in it:

2017-06-26T09:05:15.027089-07:00 INFO kernel: [23745.069396] traps: Chrome_IOThread[3790] trap invalid opcode ip:5ca378aff973 sp:79b41a89d220 error:0 in chrome[5ca377acc000+8906000]
2017-06-26T09:05:15.166527-07:00 WARNING crash_reporter[22872]: [user] Received crash notification for chrome[3743] sig 4, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)

The missing crash is probably because chrome does not call crash_reporter to dump it. A handle log line would be something like this:

2017-06-29T07:26:08.745372-07:00 WARNING crash_reporter[15337]: Received crash notification for chrome[14809] user 1000 (called directly)

I have to dig deeper to see why.

Comment 2 by xiy...@chromium.org, Jun 29 2017 

Found the following in feedkback "ui_log". Dump failed because of running out of fd.

ExceptionHandler<IPv6: 6>GenerateDump sys_pipe failed:Too many open files
ExceptionHandler<IPv6: 6>SendContinueSignalToChild sys_write failed:Bad file descriptor
ExceptionHandler<IPv6: 6>WaitForContinueSignal sys_read failed:Bad file descriptor
Failed to generate minidump.

Comment 3 by xiy...@chromium.org, Jun 29 2017 

We might be seeing issue 629521. The last CL (https://chromium-review.googlesource.com/448356) to increase Chrome max FD limit is landed on Jun 23, included in 9677.0.0 (61.0.3138.0) and above.

Comment 4 by rcui@google.com, Jun 29 2017 

Is there a tool to parse the system_logs.txt file or do we normally just go through it visually?

Comment 5 by xiy...@chromium.org, Jun 29 2017 

Not aware of any tools. I scan through it in an editor, checking "chrome_user_log", "chrome_system_log", "sys_log" and "ui_log" sections.

Comment 6 by teravest@chromium.org, Aug 16 2017

Mergedinto: 583730
Status: Duplicate (was: Untriaged)
crbug.com/583730 is open to allow us to get crash reports in these cases.

https://chromium-review.googlesource.com/c/545240 is an initial attempt to fix this, but we have to make seccomp changes for that approach to work.
►

Sign in to add a comment