Issue metadata
Sign in to add a comment
|
by_os:system_memory:java_heap reports zero on android 5 |
||||||||||||||||||||||
Issue descriptionSplitting off from issue 747915. Looks like this java_heap metric has been reporting zero pretty munch since forever for all stories on this bot. Graphs: https://chromeperf.appspot.com/report?sid=c02b152d19692fd21b71134119ec81cff17ad50c470fa9f0c191a602bfd8a585 A trace from the N5 bot shows java_heap is definitely non-zero, e.g.: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_25-2017-07-23_06-42-03-23264.html Other bots (including the downstream N5) do seem to show correct values for java_heap
,
Sep 10
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 11
This is weirdly still the case on upstream bots: https://chromeperf.appspot.com/report?sid=de8762ccfd3ac8b4c05d04efbb3e388e84fdc277c1f5f7978d1f3abc8ac1ff94 But not downstream: https://chromeperf.appspot.com/report?sid=ab45e7c291a76b981fe09c123095f4e082078e4091f6588be9e1c2bb96d46438&start_rev=1535727988&end_rev=1536649045 +ssid, any clues? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by perezju@chromium.org
, Sep 8 2017Labels: OS-Android