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

Issue 802833 link

Starred by 2 users
Status: Duplicate
Merged: issue 819418
Owner:
█ ymalik@chromium.org
(currently inactive on Chromium)
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

VR Keyboard-induced memory regression

Project Member Reported by bsheedy@chromium.org, Jan 16 2018 
Enabling the VR keyboard by default resulted in a ~7.5 MB increase in memory usage while in VR. See https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICQhNrMuAoM for example graphs.

This occurs even during WebVR, where we shouldn't be needing the keyboard at all.

Comment 1 by ddorwin@chromium.org, Jan 17 2018

Labels: M-65

Comment 2 by bsheedy@chromium.org, Feb 22 2018

Labels: VR-Perf

Comment 3 by ymalik@chromium.org, Feb 26 2018

Labels: -M-65 M-67
There's been a bunch of work on the Daydream side. Namely, they got changed the voice api they were using and got rid of some unused loading code. This should give us a few MBs back, so this is just a matter of verifying that this is the case.

Comment 4 by ymalik@chromium.org, Apr 19 2018

Mergedinto: 819418
Status: Duplicate (was: Assigned)

Comment 5 by btebbs@chromium.org, Jul 4

Components: Internals>XR
►

Sign in to add a comment