
Chrome tests for the existence of a TPM on a dedicated thread since the operation may result in disk access. Since Chrome blocks showing any UI on this check finishing, increase the thread priority to USER_BLOCKING. This results in a speedup from ~1700ms to ~1ms on my development machine. Add a FIDO log entry to measure how long the check takes. This might help some users who are seeing very long times for any UI to pop up, but that stop experiencing the bug when GPM is disabled. Bug: 396607267 Change-Id: I326812b8e086398453fe794306fa8a04341eefbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6300761 Commit-Queue: Ken Buchanan <kenrb@chromium.org> Auto-Submit: Nina Satragno <nsatragno@chromium.org> Reviewed-by: Ken Buchanan <kenrb@chromium.org> Cr-Commit-Position: refs/heads/main@{#1424806}
Chrome
This directory contains the open source, application layer of Google Chrome.
Unlike other parts of Chromium like //content, which provide framework intended to support multiple products, this directory contains code that is focused on building specific products with opinionated UX.
Specific products include:
- Chrome desktop browser for Chrome OS, Windows, Mac and Linux
- Chrome mobile browser for Android
- Chrome OS system UI
See //ios/chrome for the Chrome mobile browser for iOS, and note that code that is shared between //chrome and //ios/chrome is typically factored out into //components.