30
edits
Talk:Browser Metrics: Difference between revisions
m
→Extension issues
| Line 24: | Line 24: | ||
In practice, this means that in the event of a problem or crash or other issue, there has to be a means for Firefox to identify a likely location for it: the core, or an extension, and the relevant call or parameters involved. | In practice, this means that in the event of a problem or crash or other issue, there has to be a means for Firefox to identify a likely location for it: the core, or an extension, and the relevant call or parameters involved. | ||
I'd strongly be hoping for some kind of in-memory log of the last 40-60 seconds top-level program flow control, or hooked calls executed and returned from, or similar, something that if a crash or issue occurs even once, Firefox has some kind of diagnostic error data which can be used to | I'd strongly be hoping for some kind of in-memory log of the last 40-60 seconds top-level program flow control, or hooked calls executed and returned from, or similar, something that if a crash or issue occurs even once, Firefox has some kind of top-level diagnostic error data which can be used to help narrow down where to look and what Firefox was doing, more than just a binary crash dump. Reconciled with privacy issues we ought at least to be able to find a way for error reports to be useful in the hands of users who can't, or won't, do debugging work for us, or whose bugs prove intermittent, unreproducible, or elusive to pin down, or for users who want to quickly identify where the bug seems to be, if they can. [[User:Foxxen2|Foxxen2]] 10:26, 1 April 2006 (PST) | ||