as pointed out in the mainfesto a criteria for 1.0 would be # upward MTBF trend, all-time maximum it would be good to have a graph but at least in the report the alltime maximum should be shown now.
Reporter, is this bug still valid? The linked-to crash report is 3 years old.
I'm updating the Product and Component, since the crash analysis is not part of the Talkback client itself. Also changing the URL, since the crash analysis is now part of Talkback Public's Reports section. Just select the desired Product and then click on either the Simple Reports or Smart Analysis links on the left. Note that the Talkback client will likely be replaced by Airbag in the new future.
resetting to default owner... I'm pretty sure it's not Shiva these days. :)
er, helps if I click the radio button, too.
(In reply to comment #3) > I'm updating the Product and Component, since the crash analysis is not part of > the Talkback client itself. I think you're assuming every single crash will be reported to the site. This is rarely the case, so I believe it will be useful for the talkback client to keep mtbf/crash statistics internally.
(In reply to comment #6) > I think you're assuming every single crash will be reported to the site. This > is rarely the case, so I believe it will be useful for the talkback client to > keep mtbf/crash statistics internally. > But I believe the *mean* time between failures (MTBF) is only meaningful if you average over a large number of users, platforms, and days. Otherwise it will jump all over the place depending on how you use the browser.
(In reply to comment #7) Well there are different kinds of means. You may be interested in the mean time between failures on a specific user's system or on the systems of a small number of users. Plus, what you said does not contradict my argument, as even if you want to take the mean over many users, you still need to count the crashes that happen but aren't reported.
MTBF numbers have been inaccurate for a while (not sure exactly why), but most likely due to A LOT more users submitting bad data than we used get in Talkback reports (back at Netscape, it was mostly nightly users and internal engineers/qa...in a more controlled environment). I don't think I'm going to have time to work on this bug in the near future, but if I will try to recruit volunteers to help once I get a few "Talkback Reports" projects organized for the community.
Talkback isn't used anymore: R.Invalid now.