QA/Talkback/Topcrash Analysis: Difference between revisions

m
no edit summary
m (initial outline)
mNo edit summary
Line 13: Line 13:
==How to view topcrash reports==
==How to view topcrash reports==
# Go to http://talkback-public.mozilla.org/reports/
# Go to http://talkback-public.mozilla.org/reports/
# Click on the product (firefox, thunderbird, mozilla, camino)
# Click on the product: Firefox, Thunderbird, Mozilla or Camino.
# Choose the branch, trunk, release, etc. from the links under these three or two columns:
# Choose the branch, trunk, release, etc. from the links under these three or two columns:
#* Development: trunk builds are here
#* Development: trunk builds are here.
#* Major releases (ffox and tbird only): 1.0, 1.0.x, etc.
#* Major releases (Firefox and Thunderbird only): 1.0, 1.0.x, etc.
#* Milestone releases (also includes final mozilla releases)
#* Milestone releases: also includes final Mozilla releases.
#* Beta releases (mozilla and camino only)
#* Beta releases: Mozilla and Camino only.
# in the left side, a list of the reports available should appear, such as:
# In the left side, a list of the reports available should appear, such as:
#* Topcrashers by Build: this is the main report we'll start with
#* Topcrashers by Build: this is the main report to start with.
#* Simple Reports: this groups crashes by signature, and skimming this helps with getting additional comments/feedback.
#* Simple Reports: this groups crashes by signature, and skimming this helps with getting additional comments/feedback.
#* Smart Analysis: also grouped by signature, but also lists bug number info (where available).
#* Smart Analysis: also grouped by signature, but also lists bug number info (where available). You can add info found here to [[Talkback_Topcrash_Analysis:How_to_file_a_topcrash_bug|new topcrash bugs filed]], especially if it helps with finding a reproducible test. Note that you should skim first to see that there's no sensitive data there (eg, user accidentally typed in a passwd!) and remove that before pasting into a bug report.
# You can add info found here to new topcrash bugs we file, especially if it helps with finding a reproducible test. note that you should skim first to see that there's no sensitive data there (eg, user accidentally typed in a passwd!) and remove that before pasting into a bug report.


==How to file a topcrash bug==
==How to file a topcrash bug==
#
#
#
#
84

edits