751073 - Loading msnbc.com will freeze the Adreno200-ES20 devices

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Paul Feher]

Attachment: Log file

Nightly Fennec 15.0a1 (2012-05-01)
Device: HTC Desire
OS: Android 2.2.2

Steps to reproduce:
1. Load masnbc.com.
2. Rotate the device in landscape mode.
3. Reload the page.
4. Rotate the device in portrait mode
5. Scroll the page up/down few times.
 
Expected result:
No freeze of the OS should occur after step 5.

Actual result:
After step 5, the entire OS will be frozen. Sometimes the OS freeze could persist forever. The only solution is to pull out the battery.

NOTE:This issue is reproducible for 4 of 5 tries. Please see the log file

Comment 1

[Aaron Train [:aaronmt]]

CPU is pegged, and a 10291 ms composite?

Comment 2

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

Yeah, that 10291ms composite seems.. abnormally large.

Comment 3

[Aaron Train [:aaronmt]]

Not a whole lot of out there testable besides the HTC Desire, and the HTC Nexus One with the Adreno 200:

Assortment of non-compatible phones sporting the GPU

* Samsung Galaxy Ace S5830  (800MHz, ARMv11) 
* Samsung Galaxy Mini S5570  (600MHz, ARMv6)
* LG Optimus One P500 (600MHz, ARMv11)
* Motorola Moto XT316 (600MHZ, ARMv11)
* LG Optimus GT540 (600, ARMv6)

Now the HTC Nexus One; testing Nightly (05/02) over Gingerbread (2.3.4) using the steps to reproduce in comment #0 yield mobile scrolling performance issue (bug 749568) but I am unable to reproduce this issue reported. Could it be a mixture Froyo driver issue?

Comment 4

[Ali Juma [:ajuma]]

Based on

https://developer.qualcomm.com/forum/qdevnet-forums/mobile-gaming-graphics-optimization-adreno/11525

this appears to be an Adreno driver bug.

Paul, out of curiosity (and based on a vague recollection of having seen this before), does disabling the live wallpaper (and using a static wallpaper instead) prevent this issue?

Comment 5

[Paul Feher]

(In reply to Ali Juma [:ajuma] from comment #4)
> Based on
> 
> https://developer.qualcomm.com/forum/qdevnet-forums/mobile-gaming-graphics-
> optimization-adreno/11525
> 
> this appears to be an Adreno driver bug.
> 
> Paul, out of curiosity (and based on a vague recollection of having seen
> this before), does disabling the live wallpaper (and using a static
> wallpaper instead) prevent this issue?

The device uses a static wallpaper

Comment 6

[Kevin Brosnan [Ex-Mozilla]]

I tested this page on my G2 running 2.2 w/ Adreno 205 and the page loads quickly. This is not a 2.2 issue.

Comment 7

[JP Rosevear [:jpr]]

George, can you right a minimal test case based on #4 and see if we can confirm its a driver bug?

Ali, George, is there any thoughts on how to work around this?

Comment 8

[Ali Juma [:ajuma]]

(In reply to JP Rosevear [:jpr] from comment #7)
> George, can you right a minimal test case based on #4 and see if we can
> confirm its a driver bug?
> 
> Ali, George, is there any thoughts on how to work around this?

Once we can have a minimal test case with which we can reliably reproduce, we can see if any of the workarounds that others have posted (at the site mentioned above and elsewhere) will work for us. There doesn't appear to be a single workaround that has worked for everyone, so we'll probably need to experiment a little.

Comment 9

[Tony Chung [:tchung]]

im going to order a HTC Desire (adreno 200), to see if we can reproduce.  Also, if someone is on a nexus one, please also try to qawanted.

Comment 10

[Kevin Brosnan [Ex-Mozilla]]

Mark and Aaron have tried with the Nexus One however using Android 2.3. They could not reproduce.

Comment 11

[Kevin Brosnan [Ex-Mozilla]]

Minusing for now. QA is acquiring a HTC Desire. Renom if we get better data.

Comment 12

[Aaron Train [:aaronmt]]

Kevin/Tony, ping?

Comment 13

[Adrian Tamas (:AdrianT)]

This bug and Bug 757920 seem to be the same/result in the same issue. Also the HTC Desire has been blocked because it does not meet the minimum system requirements. Removing qawanted.

Comment 14

[Aaron Train [:aaronmt]]

(In reply to adrian tamas from comment #13)
> This bug and Bug 757920 seem to be the same/result in the same issue. Also
> the HTC Desire has been blocked because it does not meet the minimum system
> requirements. Removing qawanted.

It is not currently blocked.

Comment 15

[guigs [:guigs] PST (please needinfo me!)]

Also not blocked, this user is affected as well for this webgL: 
[https://support.mozilla.org/en-US/questions/1005515#answer-590613]

 "graphics": {
   "numTotalWindows": 1,
   "numAcceleratedWindows": 1,
   "windowLayerManagerType": "OpenGL",
   "windowLayerManagerRemote": true,
   "adapterDescription": "Model: P-02E, Product: P_02E, Manufacturer: PANASONIC, Hardware: pana3_2, OpenGL: Qualcomm -- Adreno (TM) 320 -- OpenGL ES 2.0 V@6.0 AU@  (CL@)",
   "adapterVendorID": "Qualcomm",
   "adapterDeviceID": "Adreno (TM) 320",
   "adapterRAM": "",
   "adapterDrivers": "",
   "driverVersion": "OpenGL ES 2.0 V@6.0 AU@  (CL@)",
   "driverDate": "",
   "webglRenderer": "Qualcomm -- Adreno (TM) 320",
   "info": {
     "AzureCanvasBackend": "skia",
     "AzureSkiaAccelerated": 1,
     "AzureFallbackCanvasBackend": "none",
     "AzureContentBackend": "cairo"
   }

I cheked this site: http://get.webgl.org/ I can see spinning cube with FIrefox mobile 30. And after toggle "webgl.disabled" to "TRUE", I see "it is disabled or unavailable" instead of cube.

True or false, In both cases, I cannot load this page. https://support.mozilla.org/ja/questions/1005515?fpa=1 Thank you.

Remote Debugging Log

GET https://support.mozilla.org/ja/questions/1005515 [HTTP/1.1 200 OK 1363ms] GET https://support.cdn.mozilla.net/static/css/mobile/common-min.css [HTTP/1.1 200 OK 374ms] GET https://support.cdn.mozilla.net/static/css/mobile/questions-min.css [HTTP/1.1 200 OK 375ms] GET https://support.cdn.mozilla.net/static/jsi18n/ja/javascript.js [HTTP/1.1 200 OK 484ms] GET https://support.cdn.mozilla.net/static/js/mobile/common-min.js GET https://support.cdn.mozilla.net/static/js/mobile/questions-min.js

Comment 16

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.