720125 - Corruption on some parts of the page (related to text input caret?)

Status: RESOLVED DUPLICATE of bug 721383

(Firefox for Android Graveyard :: General, defect, P2)

Description

[Martijn Wargers (dead)]

Attachment: testcase

Tested on the LG Optimus Black, Android 2.2.2.

Steps to reproduce:
- Go to testcase
- Tap randomly (somewher in the middle) on text inputs, until you see parts of the page get corrupted.

There is no good steps to reproduce, because it happens itermittenly.
Usually, it happens after tapping 5 times on one of the inputs in the testcase.

I don't even know if this is related to text inputs and focussing them. I think I've seen this happening sometimes on other pages as well, but less frequent.

I can't really remember seeing this happening in older builds.

Comment 1

[Martijn Wargers (dead)]

Attachment: Screenshot of bug

Comment 2

[Martijn Wargers (dead)]

Attachment: corruption in about:config

Comment 3

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Crashed with 2 different signatures by changing orientations panning in 2 tabs, and then clicking in the field on a nexus s but it's way too hard to reproduce.  I think it may have to do with some sort of race condition.  Possibly related to bug 720160?

Comment 4

[Martijn Wargers (dead)]

It's not necessarily limited to text inputs only, I've seen it on various pages.

Comment 5

[Martijn Wargers (dead)]

Attachment: Corruption in about:firefox

Now I got it just by going to about:firefox and tapping on the Update button.

Comment 6

[Doug Turner (:dougt)]

wierd?  possible driver issue?  I'd like to get ahold of this device.

Comment 7

[Martijn Wargers (dead)]

I got this very quickly while typing with the testcase from bug 721393: https://bugzilla.mozilla.org/attachment.cgi?id=591801

Comment 8

[Martijn Wargers (dead)]

I suspect very much that this is related to bug 721383. I see that happening with the testcase of that bug too, and here I'm seeing sometimes hangs and crashes too. This also has started around the same time as bug 721383 started.

So I guess this is a regression from bug 716415 also.