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

Issue 894327 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
wuyingbing@chromium.org
█ crepric@google.com
omrilio@chromium.org
█ blakeo@chromium.org
yhanada@chromium.org
pcovell@chromium.org
█ dvallet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Handwriting auto-commit is slow on lower-end devices

Project Member Reported by shend@chromium.org, Oct 11 
Chrome Version: 71.0.3567.0
OS: Chrome

What steps will reproduce the problem?
(1) Use a device with lower-end CPU
(2) Start handwriting

What is the expected result?
Candidates appear quickly.

What happens instead?
Candidates appear slowly, handwriting becomes laggy, composition text changes once per second, no way to stop it from typing.
latency.webm
3.8 MB View Download

Comment 1 by shend@chromium.org, Oct 11

Cc: wuyingbing@chromium.org
Hey Yingbing, is the lag coming from auto-commit or just the decoder?

On my lower-end device, it was using 200% CPU, making the system very laggy. Is there something we could do easily to improve this?

Comment 2 by shend@chromium.org, Oct 11

Cc: crepric@google.com
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 16 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-overlay/+/67730955c6b76b499e43599f7b52372ec89d18e1

commit 67730955c6b76b499e43599f7b52372ec89d18e1
Author: Yingbing Wu <wuyingbing@google.com>
Date: Tue Oct 16 17:30:45 2018
►

Sign in to add a comment