OLD | NEW |
(Empty) | |
| 1 # Chrome is slow, what do I do? |
| 2 |
| 3 ## How to file a bug |
| 4 |
| 5 * **File a bug.** To file a bug, please use |
| 6 **[the speed bug template](https://bugs.chromium.org/p/chromium/issues/entry?tem
plate=Speed%20Bug)**. |
| 7 * **Attach a trace.** The best way to get performance data to developers is to
include a trace, |
| 8 so please [follow these instructions](https://www.chromium.org/developers/ho
w-tos/trace-event-profiling-tool/recording-tracing-runs) |
| 9 to record a trace and attach it to the bug. |
| 10 * **Try TraceOnTap** the [TraceOnTap Extension](http://goto.google.com/traceon
tap) |
| 11 makes it easier to record traces and attach them to bugs. |
| 12 [Source code](https://github.com/catapult-project/catapult/tree/master/exper
imental/trace_on_tap) |
| 13 |
| 14 <!--- TODO: ## Bug SLO for perf bugs --> |
| 15 |
| 16 <!--- TODO: ## Bug Triage |
| 17 ### High level |
| 18 ### Best practices |
| 19 ### 3 step approach to Speed Triage |
| 20 ### Rotation Documentation |
| 21 ### Bug Dashboards |
| 22 ### Fixits |
| 23 --> |
OLD | NEW |