TPEGFX/Notes: Difference between revisions
< TPEGFX
Jump to navigation
Jump to search
Vincent Liu (talk | contribs) (→Crash) |
Vincent Liu (talk | contribs) (→Crash) |
||
| Line 9: | Line 9: | ||
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1346421 | *** https://bugzilla.mozilla.org/show_bug.cgi?id=1346421 | ||
*** https://bugzilla.mozilla.org/show_bug.cgi?id=1357734#c12 | *** https://bugzilla.mozilla.org/show_bug.cgi?id=1357734#c12 | ||
*** | *** Example for read access violation | ||
**** https://bugzilla.mozilla.org/show_bug.cgi?id=1343851#c10 | |||
*** Example for AssertSanity | |||
**** https://bugzilla.mozilla.org/show_bug.cgi?id=1314543#c5 | |||
== Testing == | == Testing == | ||
Revision as of 06:34, 12 May 2017
Crash
- offsite sharing - crash
- A look into mini dump/symbols
- how to load mini dump/symbols
- What help us from mini dump/symbols
- useful gdb/lldb commands
- (lldb) br com add 1 //executes commands when breakpoint was hit
- case study
- https://bugzilla.mozilla.org/show_bug.cgi?id=1346421
- https://bugzilla.mozilla.org/show_bug.cgi?id=1357734#c12
- Example for read access violation
- Example for AssertSanity
- A look into mini dump/symbols
Testing
- [pchang] run GTest subset
- ./mach gtest Layers.*
- GTEST_FILTER='Layers*' MOZ_RUN_GTEST=1 ./mach run --debug //use debugger to debug GTest
- [Michael Leu] - My workflow of building environments for reproducing bugs
Misc
- [ethan] Canvas performance
Triage
- [vliu] Triage flow listed.
- Try to reproduce
- Add keyword 'reproducible' if you can reproduce
- Ask reporter set layers.acceleration.disabled as true to try again(depends)
- Enable/Disalbe ANGLE on windows
- Compare the difference between on/off e10s.
- Tried to change the preferences to observe.
- If the issue relatives to painting or text, you can try to change the backend in about:config
- gfx.canvas.azure.backends
- gfx.content.azure.backends
- nglayout.debug.paint_flashing
- layers.draw-borders
- If the issue relatives to painting or text, you can try to change the backend in about:config
- Ask for about:support
- Ask for about:memory if memory related
- ni? people or mgr to help you
- land needed printing message for this bug to observe more information.(this action is providing solution not doing the triage)
- Change priority to P1-3 with reason
- Add gfx-noted if there is nothing you can follow up
- Try to reproduce
- Ways to observe occurrence for triage bug.
- Crash report contains Volume to count for crash rate. There is 10 times of Volume increase between each FF version.
- Install addon bugzilla-socorro-lens can easily see crash rate in graphic view on that bug.
- For Intermittent bug, Orange Factor counts for occurrence rate for that bug you observed.
- Crash report contains Volume to count for crash rate. There is 10 times of Volume increase between each FF version.
- A useful link to help you reading crash report.
- refer keyword here https://wiki.mozilla.org/Platform/GFX/TriageSchedule#Keywords