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

Issue 819418 link

Starred by 3 users
Status: Available
Owner: ----
Cc:
█ ymalik@chromium.org
█ asimjour@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression
Proj-XR



Sign in to add a comment

Upgrading to VR Keyboard 1.13 increased memory usage

Project Member Reported by bsheedy@chromium.org, Mar 7 2018 
Upgrading the VR Keyboard APK to 1.13 resulted in quite a few memory increases, usually around 2-3 MB. A number of metrics were affected, but all seem to be related to native memory usage.

Comment 1 by bsheedy@chromium.org, Mar 7 2018

Owner: ymalik@chromium.org
Status: Assigned (was: Available)
Affected graphs are available at https://chromeperf.appspot.com/group_report?bug_id=819418.

Assigning to ymalik since it's keyboard related, although my guess is that there isn't anything we can really do on our end other than wait on Daydream.

Comment 2 by ymalik@chromium.org, Mar 7 2018 

Hmm this is strange, I was expecting to see a decrease. Pinged the keyboard bug where we were discussing this.

Comment 3 by bsheedy@chromium.org, Mar 14 2018 

Issue 821886 has been merged into this issue.

Comment 4 by tiborg@chromium.org, Mar 14 2018 

More affected graphs are at https://chromeperf.appspot.com/group_report?bug_id=821886

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

Owner: asimjour@chromium.org

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

Cc: ymalik@chromium.org
 Issue 802833  has been merged into this issue.

Comment 7 by btebbs@chromium.org, Jul 4

Components: Internals>XR

Comment 8 by efoo@chromium.org, Aug 7 

Removing Internals>VR component and assigning to Internals>XR

Comment 9 by efoo@chromium.org, Aug 7

Components: -Internals>VR

Comment 10 by asimjour@chromium.org, Aug 27

Cc: asimjour@chromium.org
Owner: ----
Status: Available (was: Assigned)
►

Sign in to add a comment