Profile FreeList (chromium side)

tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py

Index: tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py
diff --git a/tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py b/tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py
index 7e7d0ffcbd7027604ea129334becd680a700f2b4..8db2bcd507dcc1f36360e96da778caafd14c81dc 100644
--- a/tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py
+++ b/tools/telemetry/telemetry/core/backends/chrome/tracing_backend.py
@@ -88,10 +88,11 @@ class TracingBackend(object):
     except \
         inspector_websocket.DispatchNotificationsUntilDoneTimeoutException \
         as err:
-      raise TracingTimeoutException(
-          'Trace data was not fully received due to timeout after %s '
-          'seconds. If the trace data is big, you may want to increase the '
-          'time out amount.' % err.elapsed_time)
+      print 'Trace data was not fully received due to timeout after %s seconds. If the trace data is big, you may want to increase the time out amount.' % err.elapsed_time
+      #raise TracingTimeoutException(

[keishi, 2015/01/27 09:42:29]

I did this because when the trace data got large, dev tools stopped responding
and the tracing json file was not produced.
By not raising an exception, the partial tracing json data is written out.

+      #    'Trace data was not fully received due to timeout after %s '
+      #    'seconds. If the trace data is big, you may want to increase the '
+      #    'time out amount.' % err.elapsed_time)
     self._is_tracing_running = False
     return self._tracing_data