Closed Bug 971355 Opened 7 years ago Closed 4 years ago

HTC T-mobile G2 - Compositor hangs when user interacts with the URL bar


(Firefox for Android :: Toolbar, defect, P5)

29 Branch



Tracking Status
firefox27 --- unaffected
firefox28 + wontfix
firefox29 --- affected
firefox30 --- affected
fennec + ---


(Reporter: kbrosnan, Assigned: snorp)



(Keywords: regression)


(3 files, 2 obsolete files)

I am not able to successfully interact with the address bar in Firefox for Android 29 and 30 using a HTC t-mobile G2 running Android 2.2. Software keyboard shows up tapping on the keyboard vibrates but no characters show up on the screen. I have tried the Google keyboard that shipped with the device and SwiftKey neither work. Hardware keyboard functions as expected.
First cut of a regression range. Which puts it in the Firefox 28 cycle.
tracking-fennec: ? → 28+
speculatively tracking for 28 since we're close to the last beta. Let's get this range down in the next few days.
Flags: needinfo?(kbrosnan)
Assignee: nobody → nchen
Kevin, can you run this build, try entering text in the address bar, and post the logcat? The app anme is "Fennec nchen"
Attached file logcat (obsolete) —
Flags: needinfo?(kbrosnan)
We've still got a few more weeks of Beta, but if the fix is speculative we'll definitely want this before next Monday's go to build. Tracking for now.
Not sure what's going on; the keyboard is making the right calls.

Kevin, does the keyboard work in web content? (i.e. if you go to SUMO and type in the search field)
Flags: needinfo?(kbrosnan)
Hmm not sure why the flags got cleared...
ANR as well in content.
Flags: needinfo?(kbrosnan)
Attached file logcat-content.txt (obsolete) —
Attached file traces.txt
Can you get the logcat from this build (Fennec nchen) when typing in the address bar?
Flags: needinfo?(kbrosnan)
Attached file logcat-java-2.txt
Logcat from typing in the address bar
Attachment #8379275 - Attachment is obsolete: true
Attachment #8380978 - Attachment is obsolete: true
Flags: needinfo?(kbrosnan)
Attached file logcat-content-2.txt
logcat from typing in content. This results in a crash.
Can track this but if there's no fix ready for next Monday's beta we'll have to push this back to 29.
So the characters are actually entered correctly, but it appears they are not being drawn to the screen. Not sure what's going on. Kevin, can you make a video of the bug?
Flags: needinfo?(kbrosnan)
Video of Aurora hanging
Flags: needinfo?(kbrosnan)
fyi - I've been experiencing something very similar to this w/Nightly on GS3 ... hangs hard and often (randomly - no STR yet) ... sometimes I have to hold the power button to reboot ...
Forgot, switched to my N7 to continue testing ... seems to be no impact there.
Erin, can you get a device to Jim?
Flags: needinfo?(elancaster)
This didn't make the Monday beta so wontfixing on FF28.
Ordered phone to be delivered to Jim, for status, please see Service Now and Look up this ticket: REQ0022844. Thank you!
The hang is happening inside the compositor, during eglSwapBuffers,

#0  0xafd0eb68 in __futex_syscall3 ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#1  0xafd10634 in __pthread_cond_timedwait_relative ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#2  0xac70f0b0 in int android::SharedBufferBase::waitForCondition<android::SharedBufferClient::LockCondition>(android::SharedBufferClient::LockCondition) ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#3  0xac70f12a in android::SharedBufferClient::lock(int) ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#4  0xac70fce6 in android::Surface::lockBuffer(android_native_buffer_t*) ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#5  0xac70fd26 in android::Surface::lockBuffer(android_native_window_t*, android_native_buffer_t*)
    () from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#6  0x80605d38 in eglLockWindowSurface ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#7  0x80a72b2a in rb_resolve ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#8  0x80a7509e in rb_surface_swap ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#9  0x80a6a004 in gl2_surface_swap ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#10 0x80a6297e in oglSwapBuffer ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#11 0x80606228 in egliSwapWindowSurface ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#12 0x80608ac0 in qeglDrvAPI_eglSwapBuffers ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#13 0x806041f0 in eglSwapBuffers ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#14 0xabe03e76 in eglSwapBuffers ()
   from /Users/nchen/jimdb-arm/lib/HT09JR207271/system/lib/
#15 0x511a2028 in fSwapBuffers (surface=0x290000, dpy=0x1, this=
    0x52fb3ed8 <mozilla::gl::sEGLLibrary>) at /Users/nchen/gecko-dev/gfx/gl/GLLibraryEGL.h:283
#16 mozilla::gl::GLContextEGL::SwapBuffers (this=<optimized out>)
    at /Users/nchen/gecko-dev/gfx/gl/GLContextProviderEGL.cpp:445
#17 0x5122d924 in mozilla::layers::CompositorOGL::EndFrame (this=0x59ef2a50)
    at /Users/nchen/gecko-dev/gfx/layers/opengl/CompositorOGL.cpp:1271
#18 0x51221c0a in mozilla::layers::LayerManagerComposite::Render (this=this@entry=0x59ef2b20)
    at /Users/nchen/gecko-dev/gfx/layers/composite/LayerManagerComposite.cpp:511
#19 0x51221d48 in EndTransaction (aFlags=<optimized out>, this=0x59ef2b20, 
    aCallback=<optimized out>, aCallbackData=<optimized out>)
    at /Users/nchen/gecko-dev/gfx/layers/composite/LayerManagerComposite.cpp:245
#20 mozilla::layers::LayerManagerComposite::EndTransaction (this=0x59ef2b20, aCallback=0x0, 
    aCallbackData=<optimized out>, aFlags=<optimized out>)
    at /Users/nchen/gecko-dev/gfx/layers/composite/LayerManagerComposite.cpp:202
#21 0x51214c0c in mozilla::layers::LayerManagerComposite::EndEmptyTransaction (this=0x59ef2b20, 
    aFlags=<optimized out>)
    at /Users/nchen/gecko-dev/gfx/layers/composite/LayerManagerComposite.cpp:197
#22 0x5121bbdc in mozilla::layers::CompositorParent::CompositeToTarget (this=this@entry=
    0x5a34a800, aTarget=aTarget@entry=0x0)
    at /Users/nchen/gecko-dev/gfx/layers/ipc/CompositorParent.cpp:678
#23 0x5121bd02 in mozilla::layers::CompositorParent::Composite (this=this@entry=0x5a34a800)
    at /Users/nchen/gecko-dev/gfx/layers/ipc/CompositorParent.cpp:616
#24 0x5121bd68 in mozilla::layers::CompositorParent::ResumeComposition (this=0x5a34a800)
    at /Users/nchen/gecko-dev/gfx/layers/ipc/CompositorParent.cpp:458
#25 0x5122384e in DispatchToMethod<mozilla::layers::CompositorParent, void (mozilla::layers::CompositorParent::*)(int, int), int, int> (arg=..., method=
    (void (mozilla::layers::CompositorParent::*)(mozilla::layers::CompositorParent * const, int, int)) 0x5121bd8d <mozilla::layers::CompositorParent::ResumeCompositionAndResize(int, int)>, 
    obj=<optimized out>) at /Users/nchen/gecko-dev/ipc/chromium/src/base/tuple.h:400
#26 RunnableMethod<mozilla::layers::CompositorParent, void (mozilla::layers::CompositorParent::*)(int, int), Tuple2<int, int> >::Run (this=<optimized out>)
    at /Users/nchen/gecko-dev/ipc/chromium/src/base/task.h:307

Looking through the relevant history, I think it may be caused by an Android bug that was fixed in Gingerbread [1]

[1] the first rev in
Assignee: nchen → nobody
Component: Keyboards and IME → Graphics, Panning and Zooming
Flags: needinfo?(elancaster)
Narrowed down to which was landed between the 20131121 and 20131122 nightlies.
Blocks: 834243
No longer blocks: 871522
Summary: HTC t-mobile G2 - software keyboard does not function in the address bar → HTC T-mobile G2 - Compositor hangs when user interacts with the URL bar
Assignee: nobody → snorp
tracking-fennec: 28+ → 32+
tracking-fennec: 32+ → +
filter on [mass-p5]
Priority: -- → P5
Pretty sure this is no longer an issue as we fixed similar things a while back. Also this was filed against a device running Android 2.2 which we don't support anymore, so that alone warrants closing out this bug. If anybody can still reproduce this on a supported device please file a new bug.
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.