Display Javascript stack trace when memory allocation fails |
||||
Issue descriptionCurrently, it is difficult to diagnose out-of-memory errors caused by Javascript code because the Chrome stack trace just shows the location inside the Javascript interpreter where the trace occurred, not the lines of actual Javascript code. When a line of Javascript causes a memory allocation failure, there would be a way to get the Javascript stack trace where the failure occurred (either through one of the profilers, or by the result being printed to the Javascript console, or some other option to view the stack trace, etc.)
,
Jan 18 2017
Pri-3 that hasn't been updated in 180+ days with status=assigned or started? Get real. I've unassigned you and marked this available. If you're truly working on this, update the priority and reassign yourself or someone who is working on this.
,
Mar 9 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 19 2018
I like sheriffbot's comment more than Ben's. It's nicer ;-). Anyhow, looks like this should be just closed as WontFix given that no-one is working on it. |
||||
►
Sign in to add a comment |
||||
Comment 1 by alph@chromium.org
, Jun 24 2016Labels: -Restrict-View-Google
Owner: jarin@chromium.org