[Docs] Host MemoryInfra images on GCS

components/tracing/docs/memory_infra.md

 # MemoryInfra
 
 MemoryInfra is a timeline-based profiling system integrated in chrome://tracing.
 It aims at creating Chrome-scale memory measurement tooling so that on any
 Chrome in the world --- desktop, mobile, Chrome OS or any other --- with the
 click of a button you can understand where memory is being used in your system.
 
 [TOC]
 
 ## Getting Started
 
  1. Get a bleeding-edge or tip-of-tree build of Chrome.
 
  2. [Record a trace as usual][record-trace]: open [chrome://tracing][tracing]
     on Desktop Chrome or [chrome://inspect?tracing][inspect-tracing] to trace
     Chrome for Android.
 
  3. Make sure to enable the **memory-infra** category on the right.
 
       ![Tick the memory-infra checkbox when recording a trace.][memory-infra-box]
 
  4. For now, some subsystems only work if Chrome is started with the
     `--no-sandbox` flag. 
     <!-- TODO(primiano) TODO(ssid): https://crbug.com/461788 -->
 
 [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]
 
 After recording a trace, you will see the **timeline view**. Timeline view
 shows:
 
  * Total resident memory grouped by process (at the top).
  * Total resident memory grouped by subsystem (at the top).
  * Allocated memory per subsystem for every process.
 
 Click one of the ![M][m-blue] dots to bring up the **analysis view**. Click
 on a cell in analysis view to reveal more information about its subsystem.
 PartitionAlloc for instance, has more details about its partitions.
 
 ![Component details for PartitionAlloc][partalloc-details]
 
 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
 
 **Columns in blue** reflect the amount of actual physical memory used by the
 process. This is what exerts memory pressure on the system.
 
  * **Total Resident**: (TODO: document this).
  * **Peak Total Resident**: (TODO: document this).
  * **PSS**: (TODO: document this).
@@ skipping 95 matching lines @@
 
 Chrome-side design docs:
 
 <iframe width="100%" height="300px" src="https://docs.google.com/a/google.com/embeddedfolderview?id=0B3KuDeqD-lVJfndSa2dleUQtMnZDeWpPZk1JV0QtbVM5STkwWms4YThzQ0pGTmU1QU9kNVk">
 </iframe>
 
 Catapult-side design docs:
 
 <iframe width="100%" height="300px" src="https://docs.google.com/a/google.com/embeddedfolderview?id=0B3KuDeqD-lVJfm10bXd5YmRNWUpKOElOWS0xdU1tMmV1S3F4aHo0ZDJLTmtGRy1qVnQtVWM">
 </iframe>