Open Bug 846979 Opened 10 years ago Updated 4 months ago

Collect telemetry for js_ReportOverRecursed count

Categories

(Core :: JavaScript Engine, defect)

defect

Tracking

()

People

(Reporter: gps, Unassigned)

Details

In bug 845842 we are dealing with stack blowout issues. Conversing with jimb on IRC it is apparent we don't know how often this occurs in the real world. He suggested I file this bug to report how often js_ReportOverRecursed is called. A similar telemetry probe would be reports on max stack sizes.
We would get a number, but it won't be a particularly useful number, nor will its trends.  I've seen many real sites that contain bugs that cause infinite recursion terminated only by the over-recursed exception.  A pattern I've seen while debugging more than once wraps the infinite recursion in a try catch and ignores the exception, causing it to be hit quite frequently.
Can we capture just chrome JS? That's what I really care about.
How about 'pages that ever blow out the stack', then? That is, only count it once, no matter how many times the exception is thrown on an individual page.

Counting distinct URLs seems like way more work than necessary; counting it per global object - such that reloading the page causes the exception to be counted again - would probably be fine.
Assignee: general → nobody
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.