[Docs] Host MemoryInfra images on GCS

The images in Drive were not world-accessible, host them on Google Cloud
Storage instead.

TBR=primiano@chromium.org

Review URL: https://codereview.chromium.org/1617703002

Cr-Commit-Position: refs/heads/master@{#370671}

3 files changed, 15 insertions, 15 deletions

diff --git a/components/tracing/docs/heap_profiler.md b/components/tracing/docs/heap_profiler.md
index ba244ce..bb46dc9 100644
--- a/components/tracing/docs/heap_profiler.md
+++ b/components/tracing/docs/heap_profiler.md
@@ -30,8 +30,8 @@ intergrated with the chrome://tracing ecosystem.
  6. Pinpoint the memory bug and live happily ever after.
 
 [memory-infra]:    memory_infra.md
-[m-purple]:        https://drive.google.com/uc?id=0Bx14iZPZRgb5RFFGc0xZZEJWVFk
-[cells-heap-dump]: https://drive.google.com/uc?id=0Bx14iZPZRgb5NGlJSFRONTFoWEU
+[m-purple]:        https://storage.googleapis.com/chromium-docs.appspot.com/d7bdf4d16204c293688be2e5a0bcb2bf463dbbc3
+[cells-heap-dump]: https://storage.googleapis.com/chromium-docs.appspot.com/a24d80d6a08da088e2e9c8b2b64daa215be4dacb
 
 ## Heap Details
 
@@ -107,8 +107,8 @@ around 72 MiB.)
 
 ![Diff of The Verge before and after loading ads][diff]
 
-[pseudo-stack]:            https://drive.google.com/uc?id=0Bx14iZPZRgb5M194Y2RqQjhoZkk
-[break-down-by-backtrace]: https://drive.google.com/uc?id=0Bx14iZPZRgb5ZDRQdGNnNDNIazA
-[break-down-by-type]:      https://drive.google.com/uc?id=0Bx14iZPZRgb5THJMYlpyTEN2Q2s
-[type-then-backtrace]:     https://drive.google.com/uc?id=0Bx14iZPZRgb5UGZFX1pDUVpOLUU
-[diff]:                    https://drive.google.com/uc?id=0Bx14iZPZRgb5UzNvMmVOa0RnQWs
+[pseudo-stack]:            https://storage.googleapis.com/chromium-docs.appspot.com/058e50350836f55724e100d4dbbddf4b9803f550
+[break-down-by-backtrace]: https://storage.googleapis.com/chromium-docs.appspot.com/ec61c5f15705f5bcf3ca83a155ed647a0538bbe1
+[break-down-by-type]:      https://storage.googleapis.com/chromium-docs.appspot.com/2236e61021922c0813908c6745136953fa20a37b
+[type-then-backtrace]:     https://storage.googleapis.com/chromium-docs.appspot.com/c5367dde11476bdbf2d5a1c51674148915573d11
+[diff]:                    https://storage.googleapis.com/chromium-docs.appspot.com/802141906869cd533bb613da5f91bd0b071ceb24
diff --git a/components/tracing/docs/memory_infra.md b/components/tracing/docs/memory_infra.md
index 58592dc..981367d 100644
--- a/components/tracing/docs/memory_infra.md
+++ b/components/tracing/docs/memory_infra.md
@@ -26,7 +26,7 @@ click of a button you can understand where memory is being used in your system.
 [record-trace]:     https://sites.google.com/a/chromium.org/dev/developers/how-tos/trace-event-profiling-tool/recording-tracing-runs
 [tracing]:          chrome://tracing
 [inspect-tracing]:  chrome://inspect?tracing
-[memory-infra-box]: https://drive.google.com/uc?export=view&id=0Bx14iZPZRgb5RHBJM1llY1g4cDg
+[memory-infra-box]: https://storage.googleapis.com/chromium-docs.appspot.com/1c6d1886584e7cc6ffed0d377f32023f8da53e02
 
 ![Timeline View and Analysis View][tracing-views]
 
@@ -47,10 +47,10 @@ The purple ![M][m-purple] dots represent heavy dumps. In these dumps, components
 can provide more details than in the regular dumps. The full details of the
 MemoryInfra UI are explained in its [design doc][mi-ui-doc].
 
-[tracing-views]:     https://drive.google.com/uc?export=view&id=0Bx14iZPZRgb5dFVYV2dtZmNxQjg
-[m-blue]:            https://drive.google.com/uc?export=view&id=0Bx14iZPZRgb5b1ZTcWY4em42a0U
-[partalloc-details]: https://drive.google.com/uc?export=view&id=0Bx14iZPZRgb5eVpPR09yTW9Ebjg
-[m-purple]:          https://drive.google.com/uc?export=view&id=0Bx14iZPZRgb5RFFGc0xZZEJWVFk
+[tracing-views]:     https://storage.googleapis.com/chromium-docs.appspot.com/db12015bd262385f0f8bd69133330978a99da1ca
+[m-blue]:            https://storage.googleapis.com/chromium-docs.appspot.com/b60f342e38ff3a3767bbe4c8640d96a2d8bc864b
+[partalloc-details]: https://storage.googleapis.com/chromium-docs.appspot.com/02eade61d57c83f8ef8227965513456555fc3324
+[m-purple]:          https://storage.googleapis.com/chromium-docs.appspot.com/d7bdf4d16204c293688be2e5a0bcb2bf463dbbc3
 [mi-ui-doc]:         https://docs.google.com/document/d/1b5BSBEd1oB-3zj_CBAQWiQZ0cmI0HmjmXG-5iNveLqw/edit
 
 ## Columns
diff --git a/components/tracing/docs/memory_infra_gpu.md b/components/tracing/docs/memory_infra_gpu.md
index c4e71ae..57f49a4 100644
--- a/components/tracing/docs/memory_infra_gpu.md
+++ b/components/tracing/docs/memory_infra_gpu.md
@@ -12,7 +12,7 @@ category and look at the _size_ column. (Not _effective size_.)
 ![Look at the size column for total GPU memory][gpu-size-column]
 
 [memory-infra]:    memory_infra.md
-[gpu-size-column]: https://drive.google.com/uc?id=0Bx14iZPZRgb5bnpuZEJOR1FwNWs
+[gpu-size-column]: https://storage.googleapis.com/chromium-docs.appspot.com/c7d632c18d90d99e393ad0ade929f96e7d8243fe
 
 ## In Depth
 
@@ -89,5 +89,5 @@ GPU category. This will show all GPU allocations, whether or not they are owned
 by another process.
 
 [cc-memory]:      /cc/memory.md
-[owner-size]:     https://drive.google.com/uc?id=0Bx14iZPZRgb5ZVRROTExMmpkaTQ
-[non-owner-size]: https://drive.google.com/uc?id=0Bx14iZPZRgb5SnNBYThUZVo0ajA
+[owner-size]:     https://storage.googleapis.com/chromium-docs.appspot.com/a325c4426422e53394a322d31b652cfa34231189
+[non-owner-size]: https://storage.googleapis.com/chromium-docs.appspot.com/b8cf464636940d0925f29a102e99aabb9af40b13