1,926
edits
No edit summary |
No edit summary |
||
| Line 38: | Line 38: | ||
As you can see, there are plenty of things to keep track of... and since I have not been able to keep up with everything on my own, I can use all the help I can get. A few people already do a lot of crash analysis on their own, but we can always use more eyes! If you have any questions, feel free to contact me. You can find me on IRC in #qa. Also, take some time to query for crash bugs in Bugzilla by looking for the "crash" and "topcrash" keywords...that should give you a good idea of what is out there now. | As you can see, there are plenty of things to keep track of... and since I have not been able to keep up with everything on my own, I can use all the help I can get. A few people already do a lot of crash analysis on their own, but we can always use more eyes! If you have any questions, feel free to contact me. You can find me on IRC in #qa. Also, take some time to query for crash bugs in Bugzilla by looking for the "crash" and "topcrash" keywords...that should give you a good idea of what is out there now. | ||
== If there is a backlog of incidents waiting to be processed on [http://talkback-public.mozilla.org/talkback/fastfind.jsp http://talkback-public.mozilla.org/talkback/fastfind.jsp], can I look at the crash info for my recent incidents on my computer? == | |||
Unfortunatly, the data is not in a human-readable format on your local machine so there is no easy way to view it. You have to wait until the Talkback Server has processed your incident before looking it up by Incident ID or finding it in any query results. | |||
edits