919598 - too-long autocomplete hangs swiftkey & fennec

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: Awesomescreen, defect)

Description

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

with a 2013-09-23 nightly (and earlier), on a 2013 Nexus 7 with the latest SwiftKey installed... if the searching/displaying results as you type takes a long time, the whole world hangs as you're typing in.

http://vice.janicek.co/x64/ is a good source of long URLs (click on Demos, click on some of the demos, ignore the crash), since they embed a good chunk of data in the URL.

Comment 1

[Aaron Train [:aaronmt]]

With SwiftKey

W/InputConnectionWrapper.ICC( 2532): Timed out waiting on IInputContextCallback
I/InputConnectionWrapper.ICC( 2532): Got out-of-sequence callback 615 (expected 616) in setExtractedText, ignoring.
I/InputDispatcher(  513): Window 'Window{427497e0 u0 InputMethod}' spent 2667.9ms processing the last input event: MotionEvent(action=1, deviceId=6, source=0x00001002, displayId=0)
W/InputConnectionWrapper.ICC( 2532): Timed out waiting on IInputContextCallback
I/InputConnectionWrapper.ICC( 2532): Got out-of-sequence callback 621 (expected 622) in setExtractedText, ignoring.
I/Choreographer( 2532): Skipped 347 frames!  The application may be doing too much work on its main thread.
I/Choreographer( 2532): Skipped 118 frames!  The application may be doing too much work on its main thread.
I/Choreographer( 2532): Skipped 59 frames!  The application may be doing too much work on its main thread.
W/InputConnectionWrapper.ICC( 2532): Timed out waiting on IInputContextCallback
I/InputConnectionWrapper.ICC( 2532): Got out-of-sequence callback 658 (expected 659) in setExtractedText, ignoring.
I/InputDispatcher(  513): Window 'Window{427497e0 u0 InputMethod}' spent 3062.7ms processing the last input event: MotionEvent(action=1, deviceId=6, source=0x00001002, displayId=0)
I/Choreographer( 2532): Skipped 358 frames!  The application may be doing too much work on its main thread.
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder( 3063): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length

With Google Keyboard, no output but just as slow. I think we have a regression with the matched URLs coming back with those long URLs.

Comment 2

[(inactive) Jim Chen [:jchen] [:darchons]]

I think it's just that the URL is really long. I see hangs in Chrome too on that site.

Maybe we can limit the URL bar text to a certain length.

Comment 3

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

It's not the length in the URL bar that's the problem; it's, theoretically, the display of the long urls in the results, or querying them.  So limiting the URL bar text to a certain length might not do anything, but limiting the URL display length in the awesomescreen results to something reasonable for the display size of the device might help.  But again, I'm just guessing as to the cause of the slowness.

Comment 4

[Ioana Chiorean]

Hey Vladimir, 
Do you still see this? The Bug 953288 landed so I think this might have been improved too. 

Thanks!

Comment 5

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

I haven't seen this in a while, so probably fixed.