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

Issue 919847 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-100% regression in webrtc_perf_tests at 26010:26010

Project Member Reported by srte@chromium.org, Jan 8

Issue description

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

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


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

webrtc-linux-large-tests
webrtc-win-large-tests
Cc: jianj@chromium.org sprang@chromium.org
The changes to vp9 are expected, but not the changes to vp8. There seems to be increase in memory usage for some of the vp8 screenshare and simulcast tests. I don't see anything obvious from the libvpx roll.

Erik do you know of any change in webrtc that would cause the vp8 change? 
I  don't see any relevant webrtc changes close to this regression. It's changes to the build system  and removal of dead code....
Status: WontFix (was: Assigned)
Was not able to reproduce the memory increase for vp8 on my linux machine, and don't see anything in the roll that would cause this. The reported regressions for vp8 memory increase are only on windows and not so large (1-3%), so will close this for now.

Sign in to add a comment