769369 - [ARMv6] Fennec loses responsiveness after time

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

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

Attachment: logcat

1. go to youtube.com
2. pan around
3. go to hulu.com
4. pan around
5. go to newground.com
6. pan around

Expected: responsive and will continue to pan
Actual: sluggish response

Comment 1

[Aaron Train [:aaronmt]]

Phone, 2.2?

Comment 2

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

Samsung GT-I5510, Android 2.2

Comment 3

[Alex Keybl [:akeybl]]

Adding qawanted to see if this still reproduces. If so, we should get mobile devs to take a look at the issues.

Comment 4

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

I don't have the device, I brought it back to mnt View so this task can be done by another QA.

Comment 5

[Alex Keybl [:akeybl]]

Kevin - would you mind taking a look or reassigning?

Comment 6

[Kevin Brosnan [Ex-Mozilla]]

I have the device with me looking at it will be down the queue as it is below the minimum specs put forth.

Comment 7

[Alex Keybl [:akeybl]]

(In reply to Kevin Brosnan [:kbrosnan] from comment #6)
> I have the device with me looking at it will be down the queue as it is
> below the minimum specs put forth.

I don't think we need to keep a hard and fast rule of minimum specs (at least for blocklisting). A quality evaluation was never given for this phone at https://wiki.mozilla.org/QA/Fennec/Armv6Compatibility, so it's unclear if the phone runs ARMv6 builds well.

If the phone functions well, we should try to fix this issue, regardless of minimum specs.

Comment 8

[Paul Feher]

This is also reproducible on Lg Optimus One P500 (Android 2.2) using the latest Nightly 18.0a1 2012-09-03. Furthermore following the same STR from comment0 using a Armv7 low-end device HTC Desire (2.2) i observed that there is no big difference in functionality between the two devices.

Comment 9

[Alex Keybl [:akeybl]]

The devices listed here are just under our draft minimum spec, so there's little reason to believe this won't happen with in-spec devices.

Brad - can you reassign for FF16 investigation?

Comment 10

[Kartikaya Gupta (email:[e-mail])]

Aaron, are you able to repro on any device we have in Toronto?

Comment 11

[Kartikaya Gupta (email:[e-mail])]

Also as a note to my future self: the first patch on bug 781883 may have helped with this, since GeckoApp was restarted 5 times over the logcat capture period.

Comment 12

[Kartikaya Gupta (email:[e-mail])]

I'm not able to reproduce on an ARMv6 Xperia running 2.3.4 and the latest nightly, so I don't think this affects all ARMv6 phones. I'll need to get my hands on a device where this is reproducible to debug it.

Comment 13

[Aaron Train [:aaronmt]]

(In reply to Kartikaya Gupta (:kats) from comment #10)
> Aaron, are you able to repro on any device we have in Toronto?

I haven't seen this on the Samsung Gio, nor the HTC Legend.

Comment 14

[Aaron Train [:aaronmt]]

(In reply to Alex Keybl [:akeybl] from comment #9)
> The devices listed here are just under our draft minimum spec, so there's
> little reason to believe this won't happen with in-spec devices.
> 
> Brad - can you reassign for FF16 investigation?

Based on where we are with the cycle, the lack of movement and the inability to reproduce this with an in-spec device, do we still want to track this?

Comment 15

[Alex Keybl [:akeybl]]

(In reply to Aaron Train [:aaronmt] from comment #14)
> (In reply to Alex Keybl [:akeybl] from comment #9)
> > The devices listed here are just under our draft minimum spec, so there's
> > little reason to believe this won't happen with in-spec devices.
> > 
> > Brad - can you reassign for FF16 investigation?
> 
> Based on where we are with the cycle, the lack of movement and the inability
> to reproduce this with an in-spec device, do we still want to track this?

Agreed, given the lack of reproducibility we'll untrack.

Comment 16

[Kartikaya Gupta (email:[e-mail])]

I'm unable to reproduce the sluggishness using the STR in comment 0 on a GT-I5510M running 2.2.2 using the latest nightly. Closing WFM; please reopen if needed.