TPEGFX/Notes

Editor

[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
- https://drive.google.com/file/d/0B29kx4ibiTBgN0JBTVBiVEh0TUU/view

[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
- 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
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.
    - bugzilla-socorro-lens
- For Intermittent bug, Orange Factor counts for occurrence rate for that bug you observed.
  - Orangefactor
Some debugging ways can help to verify the issues.
- 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
A useful link to help you reading crash report.
- Understanding-crash-reports
refer keyword here https://wiki.mozilla.org/Platform/GFX/TriageSchedule#Keywords