New issue
Advanced search Search tips

Issue 726607 link

Starred by 1 user
Status: Assigned
Owner:
tzik@chromium.org
Cc:
haraken@chromium.org
bashi@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Collect "[Renderer hang]" crash report on non-Windows platform

Project Member Reported by tzik@chromium.org, May 26 2017 
We are currently collecting the crash dump on a renderer hang only on Windows for a technical reason. However, considering the reason of renderer hang may vary for each platform, ones from other platform will be useful to chase platform specific hangs such as OOM slashing.

Comment 1 by tzik@chromium.org, May 26 2017 

To dump my ideas:
Option 1: Send SIGABRT instead of SIGTERM on the abnormal renderer termination.
Option 2: Assuming the renderer IO thread keeps alive on the main thread hang, add an IPC handler just to crash the renderer on the renderer IO thread.

(1) looks easy to implement. (2) looks not hard, and we can set a crash key before crash.
Here is a draft impl of (2): https://chromium-review.googlesource.com/c/515343
►

Sign in to add a comment