The default bug view has changed. See this FAQ.

Entering text in inputs fields has regressed in performance; lagged input

VERIFIED FIXED

Status

()

Firefox for Android
General
P1
major
VERIFIED FIXED
5 years ago
8 months ago

People

(Reporter: RemusPop, Assigned: alexp)

Tracking

({inputmethod, perf, regression})

unspecified
ARM
Android
inputmethod, perf, regression
Points:
---

Firefox Tracking Flags

(firefox11 fixed, fennec11+)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Tried to file a bug to bugzilla but typing was really slow, getting 0 fps most of the time.
Also when typing a word, capital letters would come up all of a sudden making typing almost impossible.
I am running nightly in android 2.2.1 in huawei ideos s7.
I can reproduce this on the the Galaxy Tab 10.1 (Android 3.1) using the Quick Search field, alongside my Nexus S (Android 2.3.6).

--
20111124085716
http://hg.mozilla.org/projects/birch/rev/88679504d1df
Keywords: perf, regression, regressionwindow-wanted

Updated

5 years ago
Summary: Entering text in Nightly is very slow → Entering text in inputs fields has regressed in performance; lagged input

Updated

5 years ago
Hardware: Other → ARM

Updated

5 years ago
Duplicate of this bug: 705266
This issue doesn't occur on:
20111122221128
http://hg.mozilla.org/projects/birch/rev/5b13d1ed6376

but it occurs on:
20111123205632
http://hg.mozilla.org/projects/birch/rev/98861dbb3277

Possible range:
http://hg.mozilla.org/projects/birch/pushloghtml?fromchange=5b13d1ed6376&tochange=98861dbb3277
Keywords: regressionwindow-wanted
This issue occurs on:
20111123111528
http://hg.mozilla.org/projects/birch/rev/8fcdb0e7131d

Perhaps on of the landed patches from Bug 703141 causes this bug.
(Reporter)

Comment 5

5 years ago
Also reproducible in Samsung Galaxy SII with Android 2.3.3, but capital letters or double space issues do not exist.
Today typing into google.com input:

W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
I/InputDispatcher(  240): Application is not responding: Window{4173eb48 InputMethod paused=false}.  5005.7ms since event, 5005.5ms since wait started
I/WindowManager(  240): Input event dispatching timed out sending to InputMethod
W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
D/dalvikvm( 4410): GC_CONCURRENT freed 1778K, 17% free 15263K/18375K, paused 2ms+5ms
W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
I/InputDispatcher(  240): Application is not responding: Window{4173eb48 InputMethod paused=false}.  9768.9ms since event, 5002.2ms since wait started
I/WindowManager(  240): Input event dispatching timed out sending to InputMethod
W/InputConnectionWrapper.ICC(  406): Timed out waiting on IInputContextCallback
I/InputConnectionWrapper.ICC(  406): Got out-of-sequence callback 1453 (expected 1459) in setTextBeforeCursor, ignoring.
D/GeckoInputConnection( 4410): IME: getTextAfterCursor
D/GeckoInputConnection( 4410): IME: getCursorCapsMode
D/GeckoInputConnection( 4410): IME: setComposingText
I/InputConnectionWrapper.ICC(  406): Got out-of-sequence callback 1454 (expected 1459) in setTextAfterCursor, ignoring.
I/InputConnectionWrapper.ICC(  406): Got out-of-sequence callback 1455 (expected 1459) in setCursorCapsMode, ignoring.
D/GeckoInputConnection( 4410): IME: getCursorCapsMode

This is pretty bad.

--
Samsung Nexus S (Android 4.0.1)
20111128040211
http://hg.mozilla.org/projects/birch/rev/aa6ad7ab9b43
Severity: normal → major
(Assignee)

Updated

5 years ago
Keywords: inputmethod
Another URL where it's particularly really bad, amazon.com search with an 11 second timeout on typing a few words.
Alex, can you see what could be happening here? Is it an IME issue or a reapint issue?
Assignee: nobody → alexp
Priority: -- → P1
(Assignee)

Comment 9

5 years ago
I've got a different regression window. Input is fine in the build 20111118040220, but is slow in the next nightly 20111119040305.

Tested on Nexus One. In the latter build the typed text appears with a very noticeable delay - I already stopped hammering the VKB, but the letters keep appearing one by one for several more seconds.

I will look further into this today.
(Assignee)

Comment 10

5 years ago
Apparently the performance regression was caused by the bug 703821. Backing out the change ea5e1f4e996a fixes this problem.

Aaron, could you please try my build with that change backed out and see if it behaves better in your scenarios? It is here: http://people.mozilla.org/~alexp/bug/705166-lagged-input/fennec-11.0a1.en-US.android-arm.apk
Thanks.
(In reply to Alex Pakhotin (:alexp) from comment #10)
> http://people.mozilla.org/~alexp/bug/705166-lagged-input/fennec-11.0a1.en-US.
> android-arm.apk

Indeed fixed in this build.
(Assignee)

Comment 12

5 years ago
Created attachment 577789 [details] [diff] [review]
Backing out bug 703821

Thank you for the confirmation, Aaron.

This patch just backs out the change ea5e1f4e996a.
Sounds like bug 703821 needs an alternative solution.

Patrick, what do you think?
Attachment #577789 - Flags: feedback?(pwalton)
We can't take this patch as it stands. It's better to have slow input fields than to have random display corruption all over the place.
Will bug 701623 (and bug 704575) fix this situation?

Updated

5 years ago
Attachment #577789 - Flags: feedback?(pwalton) → feedback-
(In reply to Mark Finkle (:mfinkle) from comment #14)
> Will bug 701623 (and bug 704575) fix this situation?

It ought to do, yes. I'll have a look at this.
I've fixed bug #704575, so if this could be re-tested, that'd be useful.
(In reply to Chris Lord [:cwiiis] from comment #16)
> I've fixed bug #704575, so if this could be re-tested, that'd be useful.

With https://hg.mozilla.org/projects/birch/rev/c9164cc832de, it's definately better but still somewhat slower than I can recall (at least on my Nexus S 2.3.6).

Perhaps others want to try as well.
(Assignee)

Comment 18

5 years ago
(In reply to Chris Lord [:cwiiis] from comment #16)
> I've fixed bug #704575, so if this could be re-tested, that'd be useful.

That patch makes input work much-much better! On the Asus Transformer I don't see basically any lag: the typed text appears right away even with keyboard being mashed, while without the patch it was so slow that the entered characters queued up and were appearing for several seconds after you stopped typing.
(Assignee)

Comment 19

5 years ago
I guess this bug is fixed in the latest nightly.
Aaron, can you confirm please?
Priority: P1 → --
(Assignee)

Updated

5 years ago
Priority: -- → P1
Working fine for me too
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Comment 21

5 years ago
As Brand noticed today, WORKSFORME is not a correct resolution for this one. The bug was actually fixed by the patch in bug 704575.
Resolution: WORKSFORME → FIXED
(Assignee)

Comment 22

5 years ago
> As Brand noticed today

Err, I meant Brad. :)

Comment 23

5 years ago
Retested with:
Mozilla/5.0(Android; Linux armv7l; rv:11.0a1) Gecko/20111208 Firefox/11.0a1 Fennec/11.0a1
Device: HTC Desire Z (Android 2.3)

Bug no longer reproducible. Verifying.
Status: RESOLVED → VERIFIED
tracking-fennec: --- → 11+
status-firefox11: --- → fixed
You need to log in before you can comment on or make changes to this bug.