Tab Search: Add used_js_heap_size_begin and used_js_heap_size_end

metrics

Bug: 1099917
Change-Id: Ic79d19cd576f97223d01021d1af5d3e0a2579c76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2612112Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Commit-Queue: Yuheng Huang <yuhengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841946}

tools/perf/page_sets/tab_search/tab_search_story.py

@@ -104,7 +104,10 @@ class TabSearchStory(page.Page):
     tab.WaitForDocumentReadyStateToBeComplete()
 
     # Send key navigation to Tab Search bubble.
+    action_runner.ExecuteJavaScript(MEASURE_JS_MEMORY %
+                                    'used_js_heap_size_begin')
     self.InteractWithPage(action_runner)
+    action_runner.ExecuteJavaScript(MEASURE_JS_MEMORY % 'used_js_heap_size_end')
 
   def InteractWithPage(self, action_runner):
     self.ScrollTabs(action_runner)
@@ -294,3 +297,8 @@ window.__webui_startMeasuringFrameTime('%s')
 STOP_MEASURING_FRAME_TIME = '''
 window.__webui_stopMeasuringFrameTime()
 '''
+
+MEASURE_JS_MEMORY = '''
+performance.mark(
+    `%s:${performance.memory.usedJSHeapSize}:benchmark_value`);
+'''