New issue
Advanced search Search tips

Issue 749986 link

Starred by 2 users
Status: WontFix
Owner:
ilnik@chromium.org
Closed: Aug 2017
Cc:
sprang@chromium.org
mflodman@chromium.org
brandtr@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug-Regression



Sign in to add a comment

3.2% regression in webrtc_perf_tests at 19129:19129

Project Member Reported by sprang@google.com, Jul 28 2017 
I think r19129 is unlikely to be a culprit.
It could however make sense that 19130 causes some increased memory usage, but since it's only test framework memory increase it's probably ok.

Setting low prio, ilnik@ please close at your convenience if you agree.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 28 2017 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=749986

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=bc37f7086a452d398ae99b56dea5f1dea58571c6039ca7e8c91485fc1b13399e


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

webrtc-win-large-tests

Comment 2 by sprang@chromium.org, Jul 28 2017

Components: Blink>WebRTC>Video
Labels: OS-All Pri-3
webrtc:r19130 https://codereview.webrtc.org/2976373002

Comment 3 by ilnik@chromium.org, Aug 17 2017

Status: WontFix (was: Assigned)
The memory usage growth looks consistent with storing an additional uncompressed frame in the memory, which is the case in that CL.
►

Sign in to add a comment