Using HardwareRenderer to draw omnibar instead of Canvas API

This CL is an attempt to fix crashes caused by migrating the
renderer to hardware accelerated drawing, replacing the
Canvas API calls with the HardwareRenderer call, the gains
in drawing time observed after the migration are still
observed with the new API.

This is controlled by --enable-features=ToolbarUseHardwareBitmapDraw
and only works on Android 10 or higher.

This was tested via generating traces with software/hardware
drawing, using the same query used for the previous CL.
https://crrev.com/c/2611455/37

SELECT
  AVG(dur), min(dur), max(dur), count(*)
FROM slice
WHERE name LIKE "%captureWithHard%" AND (
  SELECT
    descendant.id
  FROM DESCENDANT_SLICE(slice.id) AS descendant
  LIMIT 1
) IS NOT NULL;

HardwareDraw
AVG(dur)	min(dur)	max(dur)	count(*)
2968600	990000	5943000	5
3757500	1626000	5303000	4
2755400	890000	5658000	5


SELECT
  AVG(dur), min(dur), max(dur), count(*)
FROM slice
WHERE name LIKE "%captureWithSoft%" AND (
  SELECT
    descendant.id
  FROM DESCENDANT_SLICE(slice.id) AS descendant
  LIMIT 1
) IS NOT NULL;
SoftwareDraw
AVG(dur)	min(dur)	max(dur)	count(*)
9798200	3079000	14491000	5
9942500	3976000	17231000	6
9981800	3458000	14530000	5

Bug: b/193501524,1185197
Change-Id: I7a2d8f1388e368c3ffa1857854744802de7b193c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3452087
Reviewed-by: Stephen Nusko <nuskos@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Omar Elmekkawy <mekk@google.com>
Cr-Commit-Position: refs/heads/main@{#971726}
1 file changed
tree: 846db9d9f59fa34048b566a6aabd46d78697a720
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.