Issue metadata
Sign in to add a comment
|
OOM Accountability for Browser: Stack annotation for crash reports giving source origin for work that caused crash. |
||||||||||||||||||||||||
Issue descriptionOOM issues in the browser often involve unexpected API usage from a given domain or origin. Somehow including this information in crash reporting or stack traces would greatly help debug & narrow down crashes and OOM crashes that we don't know the root cause. Action item from postmortem: https://docs.google.com/document/d/1PphqDNEMLueeTtK5OZDN4HtnQ_hrRHEEQXmyr-C8ST0/edit
,
May 4 2017
This requires attribution of tasks to domains/origins, which needs deep LuckyLuke/Blink scheduler integration.
,
May 3 2018
This was done in issue 825987 . The PendingTask object on the stack has a |task_backtrace| member which holds the symbols of the parent from_here (well actually of the last 4 parents if this was a task posted by a task posted by a task posted by a task). |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dmu...@chromium.org
, May 3 2017