canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,714
edits
TestEngineering/Performance/Triage Process: Difference between revisions
TestEngineering/Performance/Triage Process (view source)
Revision as of 12:52, 19 March 2020
, 19 March 2020→How to handle intermittent bugs which cover a crash of Firefox?: Added missing malloc handling
(→How to handle intermittent bugs which cover a crash of Firefox?: Add some more details for skipping crash frames) |
(→How to handle intermittent bugs which cover a crash of Firefox?: Added missing malloc handling) |
||
| Line 32: | Line 32: | ||
* For a header file (.h) you can most likely continue to the next frame | * For a header file (.h) you can most likely continue to the next frame | ||
* If it is inter-process communication (IPC) related remember that various components make use of it, so check higher in the stack, which code calls into the IPC code. | * If it is inter-process communication (IPC) related remember that various components make use of it, so check higher in the stack, which code calls into the IPC code. | ||
* For allocation issues (like OOM) also find the appropriate caller | |||
When you found the final frame, search for the associated file name in searchfox, and find the corresponding Bugzilla component within the nearest moz.build file. If not done yet, also add a comment with the link to the exact crash location. Make sure to keep the changeset id in the URL. | When you found the final frame, search for the associated file name in searchfox, and find the corresponding Bugzilla component within the nearest moz.build file. If not done yet, also add a comment with the link to the exact crash location. Make sure to keep the changeset id in the URL. | ||