Google Git
Sign in
chromium / chromium / src / 85f3d2877882044d4525348acfa825e6579ef6cb
commit85f3d2877882044d4525348acfa825e6579ef6cb[log] [tgz]
authorMason Freed <masonf@chromium.org>Mon Feb 14 02:08:22 2022
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Feb 14 02:08:22 2022
tree57b771c9db28b8bf84e187ca9713af538448bbcc
parenta966a692565d8cd1bcdf1158ed04e6efecf576ad [diff]
Add token and byte counts to PumpTokenizer traces

It is often helpful in exploring parser behavior to know how many
bytes are queued, how many were parsed, and how many tokens were
parsed in a single pump session. This CL adds those metrics to
the trace event for HTMLDocumentParser::PumpTokenizer.

To implement this, I had to add a "next" pointer to the
SegmentedString class, so that HTMLInputStream can walk the
entire input stream to get a size. This walk is only done when
tracing is enabled, to avoid any performance penalty.

Bug: 1041006
Change-Id: I7be74b67f7ae3b3f8535ebb69c276eaa1a9e425c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3451357
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#970454}
3 files changed
tree: 57b771c9db28b8bf84e187ca9713af538448bbcc
  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.