| commit | c409e7c1320a2ab19e4820a19d1378bf0306ddcc | [log] [tgz] |
|---|---|---|
| author | Benoît Lizé <lizeb@chromium.org> | Tue Apr 08 09:09:10 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 08 09:09:10 2025 |
| tree | dbb8c0234f1f11dde84ee5032a9fa82004d024f7 | |
| parent | 985b83dca92e1db23728a500a9fac8385b5442f5 [diff] |
[mojo] Prevent BigBuffers from being copied into traces BigBuffers can be, well, big. However, since they support iteration, their content end up being copied byte by byte into traces. This has several drawbacks: - Slow down production code when tracing is enabled - Create enormous traces - Crashes the UI when selecting such a slice To avoid that, specialize trace value serialization for BigBuffer to only provide the size. Change-Id: Ib023a7674ba030e2b3499541a06fe08c188d8fa4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6429688 Commit-Queue: Benoit Lize <lizeb@chromium.org> Reviewed-by: Andrea Orru <andreaorru@chromium.org> Cr-Commit-Position: refs/heads/main@{#1444013}
ChromiumChromium 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.