diff --git a/AUTHORS b/AUTHORS index 5f39e1a0a50c5f..f5e92c881428fe 100644 --- a/AUTHORS +++ b/AUTHORS @@ -55,6 +55,7 @@ Amey Jahagirdar Amit Sarkar Amogh Bihani Amos Lim +Amos Lim Amruth Raj Amruth Raj Anand Ratn @@ -242,7 +243,6 @@ Erik Sjölund Eriq Augustine Ernesto Mudu Etienne Laurin -Euisang Lim Evan Peterson Evan Wallace Evangelos Foutras diff --git a/docs/chromoting_android_hacking.md b/docs/chromoting_android_hacking.md index 44a9c8891ce257..540444b4011e7d 100644 --- a/docs/chromoting_android_hacking.md +++ b/docs/chromoting_android_hacking.md @@ -1,7 +1,7 @@ # Chromoting Android Hacking This guide, which is meant to accompany the -[compilation guide](chromoting_build_instructions.md), explains the process of +[compilation guide](old_chromoting_build_instructions.md), explains the process of viewing the logs and debugging the CRD Android client. I'll assume you've already built the APK as described in the aforementioned guide, that you're in the `src/` directory, and that your binary is at diff --git a/docs/memory/tools.md b/docs/memory/tools.md index 8b3d2c0c1d5f15..cd24d6e13a3e8b 100644 --- a/docs/memory/tools.md +++ b/docs/memory/tools.md @@ -26,7 +26,7 @@ If that seems like a lot of tools and complexity, it is [but there's a reason](# ----------- ## Global Memory Dumps Many Chrome subsystems implement the -[`trace_event::MemoryDumpProvider`](../../ase/trace_event/memory_dump_provider.h) +[`trace_event::MemoryDumpProvider`](../../base/trace_event/memory_dump_provider.h) interface to provide self-reported stats detailing their memory usage. The Global Memory Dump view provides a snapshot-oriented view of these subsystems that can be collected and viewed via the chrome://tracing infrastructure. @@ -123,7 +123,7 @@ TODO(awong): Write about options to script and the flame graph. Heap dumps provide extremely detailed data about object allocations and is useful for finding code locations that are generating a large number of live allocations. Data is tracked and recorded using the [Out-of-process Heap -Profiler (OOPHP)](../../src/components/services/heap_profiling/README.md). +Profiler (OOPHP)](../../components/services/heap_profiling/README.md). For the Browser and GPU process, this often quickly finds objects that leak over time. @@ -138,7 +138,7 @@ looking similar due to the nature of DOM node allocation. `VirtualAlloc()`) will not be tracked. * Utility processes are currently not profiled. * Allocations are only recorded after the - [HeapProfilingService](../../src/components/services/heap_profiling/heap_profiling_service.h) + [HeapProfilingService](../../components/services/heap_profiling/heap_profiling_service.h) has spun up the profiling process and created a connection to the target process. The HeapProfilingService is a mojo service that can be configured to start early in browser startup but it still takes time to spin up and early diff --git a/docs/speed/benchmark/harnesses/webrtc_perf.md b/docs/speed/benchmark/harnesses/webrtc_perf.md index e54dbee9037206..07523bfc59f5f2 100644 --- a/docs/speed/benchmark/harnesses/webrtc_perf.md +++ b/docs/speed/benchmark/harnesses/webrtc_perf.md @@ -10,14 +10,14 @@ For its telemetry benchmarks, WebRTC uses the [WebRTC GitHub project](https://github.com/webrtc). These are downloaded by the -[`update_webrtc_cases`](../../../tools/perf/page_sets/update_webrtc_cases) +[`update_webrtc_cases`](../../../../tools/perf/page_sets/update_webrtc_cases) script into the -[`webrtc_cases`](../../../tools/perf/page_sets/webrtc_cases/) +[`webrtc_cases`](../../../../tools/perf/page_sets/webrtc_cases/) directory, and then referenced in -[`webrtc_cases.py`](../../../tools/perf/page_sets/webrtc_cases.py), +[`webrtc_cases.py`](../../../../tools/perf/page_sets/webrtc_cases.py), which controls the user interactions and duration of the test. -The [`webrtc.py`](../../../tools/perf/benchmarks/webrtc.py) +The [`webrtc.py`](../../../../tools/perf/benchmarks/webrtc.py) benchmark specifies which metrics should be collected for the test pages, and extra options that we pass to the test to fake the real camera and skip assing permission to get access to the video and audio from the user. @@ -36,7 +36,7 @@ To collect traces and compute metrics you can run the following command You can filter the pages you want to test using the `--story-tag-filter` flag with the tags specified in -[`webrtc_cases.py`](../../../tools/perf/page_sets/webrtc_cases.py#127). +[`webrtc_cases.py`](../../../../tools/perf/page_sets/webrtc_cases.py#127). For example, to run only the *multiple-peerconnections* test page, you can use the following command: @@ -63,7 +63,7 @@ gh-pages branch.** See the *[multiple-peerconnections](https://github.com/webrtc/test-pages/tree/gh-pages/src/multiple-peerconnections)* test page for an example. -2. **Edit the [`update_webrtc_cases_script`](../../../tools/perf/page_sets/update_webrtc_cases#21) +2. **Edit the [`update_webrtc_cases_script`](../../../../tools/perf/page_sets/update_webrtc_cases#21) to reference the page you added, and run it.** This will download the `index.html` file and the `main.js` file into the @@ -76,11 +76,11 @@ to reference the page you added, and run it.** interactions.** See the - [`MultiplePeerConnections`](../../../tools/perf/page_sets/webrtc_cases.py#101) + [`MultiplePeerConnections`](../../../../tools/perf/page_sets/webrtc_cases.py#101) class for example. 4. **Add the story to the `WebrtcPageSet` class.** - See [here](../../../tools/perf/page_sets/webrtc_cases.py#127) for example. + See [here](../../../../tools/perf/page_sets/webrtc_cases.py#127) for example. 5. **Submit your changes as a CL** diff --git a/docs/webui_explainer.md b/docs/webui_explainer.md index b9bb5a7205b6e8..72507c050c32aa 100644 --- a/docs/webui_explainer.md +++ b/docs/webui_explainer.md @@ -655,7 +655,7 @@ are in flight. ## See also -* WebUI's C++ code follows the [Chromium C++ styleguide](../c++/c++.md). +* WebUI's C++ code follows the [Chromium C++ styleguide](../styleguide/c++/c++.md). * WebUI's HTML/CSS/JS code follows the [Chromium Web Development Style Guide](../styleguide/web/web.md)