df9383cb3c
chore: add a TRACE call for crash_reporter::Start() Initializing the crashReporter takes around 620 milliseconds on Intel macOS. I have sent a CL to crashpad to partially fix the performance issue in https://chromium-review.googlesource.com/c/crashpad/crashpad/+/3641386. It would be beneficial to log the performance impact of this function in the traces in case this slows down in the future. Signed-off-by: Darshan Sen <raisinten@gmail.com> |
||
|---|---|---|
| .. | ||
| app | ||
| browser | ||
| common | ||
| renderer | ||
| utility | ||