New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 672110 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

No data received for memory.top_10_mobile_stress from android-nexus7v2 since 433674

Project Member Reported by tdres...@chromium.org, Dec 7 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=672110

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZy4AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrEBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGVfc3RyZXNzL21lbW9yeTpjaHJvbWU6YWxsX3Byb2Nlc3NlczpyZXBvcnRlZF9ieV9jaHJvbWU6Z3B1OmVmZmVjdGl2ZV9zaXplX2F2Zy9iYWNrZ3JvdW5kL2FmdGVyX2h0dHBfd3d3X2JhaWR1X2NvbV9zX3dvcmRfZ29vZ2xlDAsSDVN0b3BwYWdlQWxlcnQYirwaDA,agxzfmNocm9tZXBlcmZy3QELEhNTdG9wcGFnZUFsZXJ0UGFyZW50Iq4BQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHU6ZWZmZWN0aXZlX3NpemVfYXZnL2JhY2tncm91bmQvYWZ0ZXJfaHR0cF93d3dfYmFpZHVfY29tX3Nfd29yZF9nb29nbGVfcmVmDAsSDVN0b3BwYWdlQWxlcnQY9b4aDA,agxzfmNocm9tZXBlcmZy5AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrUBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGVfc3RyZXNzL21lbW9yeTpjaHJvbWU6YWxsX3Byb2Nlc3NlczpyZXBvcnRlZF9ieV9jaHJvbWU6Z3B1OmVmZmVjdGl2ZV9zaXplX2F2Zy9iYWNrZ3JvdW5kL2FmdGVyX2h0dHBfbV95b3V0dWJlX2NvbV9yZXN1bHRzX3Ffc2NpZW5jZQwLEg1TdG9wcGFnZUFsZXJ0GI3AGgw,agxzfmNocm9tZXBlcmZy_AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50Is0BQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGVfc3RyZXNzL21lbW9yeTpjaHJvbWU6YWxsX3Byb2Nlc3NlczpyZXBvcnRlZF9ieV9jaHJvbWU6Z3B1OmVmZmVjdGl2ZV9zaXplX2F2Zy9iYWNrZ3JvdW5kL2FmdGVyX2h0dHBzX21vYmlsZV90d2l0dGVyX2NvbV9qdXN0aW5iaWViZXJfc2tpcF9pbnRlcnN0aXRpYWxfdHJ1ZQwLEg1TdG9wcGFnZUFsZXJ0GMbCGgw,agxzfmNocm9tZXBlcmZy5wELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrgBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGVfc3RyZXNzL21lbW9yeTpjaHJvbWU6YWxsX3Byb2Nlc3NlczpyZXBvcnRlZF9ieV9jaHJvbWU6Z3B1OmVmZmVjdGl2ZV9zaXplX2F2Zy9iYWNrZ3JvdW5kL2FmdGVyX2h0dHBfeWFuZGV4X3J1X3RvdWNoc2VhcmNoX3RleHRfc2NpZW5jZQwLEg1TdG9wcGFnZUFsZXJ0GJHDGgw,agxzfmNocm9tZXBlcmZy5AELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrUBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHU6ZWZmZWN0aXZlX3NpemVfYXZnL2JhY2tncm91bmQvYWZ0ZXJfaHR0cF95YW5kZXhfcnVfdG91Y2hzZWFyY2hfdGV4dF9zY2llbmNlX3JlZgwLEg1TdG9wcGFnZUFsZXJ0GJnDGgw,agxzfmNocm9tZXBlcmZy5wELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrgBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHU6ZWZmZWN0aXZlX3NpemVfYXZnL2JhY2tncm91bmQvYWZ0ZXJfaHR0cF9tX2ludGxfdGFvYmFvX2NvbV9ncm91cF9wdXJjaGFzZV9odG1sX3JlZgwLEg1TdG9wcGFnZUFsZXJ0GLHFGgw,agxzfmNocm9tZXBlcmZy4wELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrQBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGVfc3RyZXNzL21lbW9yeTpjaHJvbWU6YWxsX3Byb2Nlc3NlczpyZXBvcnRlZF9ieV9jaHJvbWU6Z3B1OmVmZmVjdGl2ZV9zaXplX2F2Zy9iYWNrZ3JvdW5kL2FmdGVyX2h0dHBfd3d3X2FtYXpvbl9jb21fZ3BfYXdfc19rX25leHVzDAsSDVN0b3BwYWdlQWxlcnQYr8YaDA,agxzfmNocm9tZXBlcmZy4QELEhNTdG9wcGFnZUFsZXJ0UGFyZW50IrIBQ2hyb21pdW1QZXJmL2FuZHJvaWQtbmV4dXM3djIvbWVtb3J5LnRvcF8xMF9tb2JpbGUvbWVtb3J5OmNocm9tZTphbGxfcHJvY2Vzc2VzOnJlcG9ydGVkX2J5X2Nocm9tZTpncHU6ZWZmZWN0aXZlX3NpemVfYXZnL2JhY2tncm91bmQvYWZ0ZXJfaHR0cF9lbl9tX3dpa2lwZWRpYV9vcmdfd2lraV9TY2llbmNlX3JlZgwLEg1TdG9wcGFnZUFsZXJ0GKbHGgw


Bot(s) for this bug's original alert(s):

android-nexus7v2
Cc: perezju@chromium.org
There's no official owner, perezju@ appears to be closest.

From a recent run (https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus7v2%20Perf%20%283%29/builds/3604/steps/memory.top_10_mobile_stress/logs/json.output)

        "after_https_mobile_twitter_com_justinbieber_skip_interstitial_true": {
          "description": "total effective size reported by Chrome for the GPU process in Chrome", 
          "grouping_keys": {
            "phase": "background"
          }, 
          "important": false, 
          "improvement_direction": "down", 
          "name": "memory:chrome:gpu_process:reported_by_chrome:effective_size_avg", 
          "page_id": 13, 
          "std": 118689.25814916866, 
          "tir_label": "background", 
          "type": "list_of_scalar_values", 
          "units": "sizeInBytes", 
          "values": [
            15338668, 
            15030660, 
            15084724, 
            15127052, 
            15192876
          ]
        }, 

I'm not sure why this isn't getting reported on the dashboard.
Cc: sullivan@chromium.org
Owner: primiano@chromium.org
Status: Assigned (was: Untriaged)
TL;DR: It's probably all fine. Assigning to Primiano to double check.

All of these are on reported_by_chrome:gpu while on background, and other metrics are still reporting:
https://chromeperf.appspot.com/report?sid=df89f3047ac0f6c7b32f7347328454d5756efab4a7b9be6f8b1584eaa19b3613&start_rev=421711&end_rev=436526

So it's probably an expected side effect of Chrome no longer using gpu memory in those cases.

It's strange, however, that the gpu metric also vanished on some ref builds, e.g.:
https://chromeperf.appspot.com/report?sid=df89f3047ac0f6c7b32f7347328454d5756efab4a7b9be6f8b1584eaa19b3613&start_rev=421711&end_rev=436526

Annie, was there a recent update on ref builds?
Cc: aiolos@chromium.org
+aiolos did update the ref build recently
Status: WontFix (was: Assigned)
the benchmark is no more

Sign in to add a comment