commit | 8231d973f79e191dfd9dbc4628eefc2c239b5ce6 | [log] [tgz] |
---|---|---|
author | Wez <wez@chromium.org> | Mon Aug 23 12:33:59 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 23 12:33:59 2021 |
tree | 2bb53bfe95a92d58293c208e97535e26f2cbb25d | |
parent | 9f7912076107a7623ac455b4ca8fb2c31ee2fa3e [diff] |
Reland "[fuchsia] Publish memory usage details to Inspect." This reverts commit 85681bfa15eb915b1d3b1d93d5e26306001b2eeb. Reason for revert: Original CL was reverted speculatively to address Linux test failures, despite only affecting Fuchsia. Original change's description: > Revert "[fuchsia] Publish memory usage details to Inspect." > > This reverts commit 3fa3172fdddfeff8de140b8b81c1d27d6c14e19e. > > Reason for revert: The CL likely caused service_unittests failures. > https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20(1)/40578/test-results > [ RUN ] TracingObserverProtoTest.AddChromeDumpToTraceIfEnabled_When_TraceLog_Disabled > FATAL services_unittests[31665:31712]: [sequence_checker.h(136)] Check failed: checker.CalledOnValidSequence(&bound_at). > #0 0x557c6c97d3db in backtrace /b/s/w/ir/cache/builder/src/third_party/llvm/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:4192:13 > #1 0x557c7761a0d9 in base::debug::CollectStackTrace(void**, unsigned long) ./../../base/debug/stack_trace_posix.cc:867:39 > #2 0x557c773a7583 in StackTrace ./../../base/debug/stack_trace.cc:200:12 > #3 0x557c773a7583 in base::debug::StackTrace::StackTrace() ./../../base/debug/stack_trace.cc:197:28 > > > Original change's description: > > [fuchsia] Publish memory usage details to Inspect. > > > > Set up a "memory" node published by each web_instance, that will gather > > details from the instance's processes regarding their memory usage, on- > > demand. > > > > By default this reports the type and Private Memory Footprint of each > > process. Additional detail can be included, from named allocator-dumps > > specified in an |allocator-dump-names| argument in the web_instance's > > config-data. > > > > Bug: 1238889 > > Change-Id: Id517c52650653e1a1dd681a721d845d6bd301545 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3094003 > > Commit-Queue: Wez <wez@chromium.org> > > Auto-Submit: Wez <wez@chromium.org> > > Reviewed-by: Chris Hamilton <chrisha@chromium.org> > > Reviewed-by: David Dorwin <ddorwin@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#914113} > > Bug: 1238889 > Change-Id: I4dbc3d2bbc752709c105c4919f7df61ae55fb3cb > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3110459 > Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> > Owners-Override: Maxim Kolosovskiy <kolos@chromium.org> > Auto-Submit: Maxim Kolosovskiy <kolos@chromium.org> > Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org> > Cr-Commit-Position: refs/heads/main@{#914261} Bug: 1238889 Change-Id: I4052da8a2849379e24cea6bdc883249bbe579679 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3113669 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Wez <wez@chromium.org> Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org> Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org> Owners-Override: Maxim Kolosovskiy <kolos@chromium.org> Cr-Commit-Position: refs/heads/main@{#914285}
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.