84
edits
QA/Talkback/Topcrash Analysis: Difference between revisions
→How to file a topcrash bug
| Line 32: | Line 32: | ||
# While filing the bug in Bugzilla, make sure the summary has the following format: '''branch''' '''[@ Stack:Signature()]'''[...] - '''bug_summary''' | # While filing the bug in Bugzilla, make sure the summary has the following format: '''branch''' '''[@ Stack:Signature()]'''[...] - '''bug_summary''' | ||
#* '''branch''' is the specific branch (e.g., FX102, TB10x, Trunk, M176, etc.). | #* '''branch''' is the specific branch (e.g., FX102, TB10x, Trunk, M176, etc.). | ||
#* '''[@ Stack:Signature()]''' is | #* '''[@ Stack:Signature()]''' is each stack signature from Talkback, enclosed in [] with @ followed by a whitespace preceding the signature. You can also have multiple signatures in the summary. Note that you need not include the following in the signature: | ||
#** parenthesis in functions () | #** parenthesis in functions () | ||
#** call line numbers from functions | #** call line numbers from functions | ||
#** + signs | #** + signs | ||
#** 0x00000000 or other memory offsets | #** 0x00000000 or other memory offsets | ||
#* '''bug_summary''' is, where applicable, the actual summary of the bug. | #* '''bug_summary''' is, where applicable, the actual summary of the bug. If the bug was filed before topcrash analysis found it, it's fine to have this part of the summary at the beginning. | ||
#* Example: '''Crash in aviary builds using Linkification extension - FF10X [@ js_GC][@ js_LinkFunctionObject]''' | |||
# The bug should also include the '''crash''' and '''topcrash''' keywords. If any of the comments have reproducible test steps, go ahead and use '''topcrash+'''. | # The bug should also include the '''crash''' and '''topcrash''' keywords. If any of the comments have reproducible test steps, go ahead and use '''topcrash+'''. | ||
# Go through either the Smart Analysis and/or Simple Reports pages to gather the bug content: | |||
## Paste a link to a list of the Talkback incidents; simply copy the link for the corresponding '''Total''' number from the Topcrash Report page. | |||
## Where applicable, enter a summary of users' comments; if there are reproducible steps, do add them here. | |||
## Paste the first frame for the most commonly reported crashes for the given signature. This will make it easier to query Bugzilla for the bug. | |||
# Choose the platform/OS based on the frequency of crashes listed under '''Lin''' (Linux), '''Win''' (Windows) and '''Mac''' —again, this in the Topcrash Reports page, currently on the right side of the table. | |||
# Copy and paste the entire Smart Analysis content for the given signature into a separate text file, then attach it to the bug. This is useful if the stacks are quite long (or varying) or if there are a lot of user comments. | |||
# Repeat steps 7-9 for other signatures which are similar or seem related to the bug. | |||