739584 - Loading http://www.kevs3d.co.uk/dev/ will freeze and shut down the device

Status: RESOLVED DUPLICATE of bug 743247

(Firefox for Android Graveyard :: General, defect)

Description

[Cristian Nicolae (:xti)]

Attachment: alogcat - Nightly

Firefox 14.0a1 (2012-03-27)
Device: Samsung Galaxy S
OS: Android 2.2

Possible steps to reproduce:
1. Open Fennec
2. Go to http://www.kevs3d.co.uk/dev/
3. Tap on URL Bar for Awesomebar
4. Tap device back button
5. Perform some panning and zooming actions

Expected result:
No freeze or system failure should occur after step 5.

Actual result:
After step 5, the entire OS will be frozen. The following error is displayed in console over and over until will shut down the device:

E/IMGSRV  ( 2478): PVRSRVEventObjectWait  Timeout!
E/IMGSRV  ( 2478): PVRSRVEventObjectWait  Timeout!
E/IMGSRV  ( 2478): PVRSRVEventObjectWait  Timeout!
W/SharedBufferStack( 3998): waitForCondition(DequeueCondition) timed out (identity=117, status=0). CPU may be pegged. trying again.

Also I noticed high values for:

I/Gecko   ( 3998): Compositor: Composite took 503 ms.
I/Gecko   ( 3998): Compositor: Composite took 559 ms.
I/Gecko   ( 3998): Compositor: Composite took 236 ms.
I/Gecko   ( 3998): Compositor: Composite took 285 ms.

This issue will occur after a couple of minutes while step 5 is performed. Please see the attached log.

Note:
Sometimes the OS freeze could persist forever. The only solution is to pull out the battery.

Comment 1

[Catalin Suciu [:csuciu]]

Also reproducible on Samsung Galaxy SII (Android 2.3.4)
                     Nightly 14.0a1 (2012-03-27)

Comment 2

[Aaron Train [:aaronmt]]

Unable to reproduce on the Galaxy Nexus (Android 4.0.2). Is there a particular demo on the posted URL you ran?

Comment 3

[Cristian Nicolae (:xti)]

(In reply to Aaron Train [:aaronmt] from comment #2)
> Unable to reproduce on the Galaxy Nexus (Android 4.0.2). Is there a
> particular demo on the posted URL you ran?

No, just loading that URL mentioned in comment #comment 0. Since this bug will shut down the device and even more, will left the OS in a bad state after restarting the device, imho this is a blocker.

Comment 4

[Aaron Train [:aaronmt]]

Scanning your log I see plenty of NullPointerExceptions happening in LayerController -- perhaps a bad conversion?

Comment 5

[Johnathan Nightingale [:johnath]]

We need to get clearer on what's going on here - qawanted and beta+

Comment 6

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

I can't seem to reproduce this on the Galaxy S II.  Will need to use the Captivate.

Comment 7

[Cristian Nicolae (:xti)]

Here is a video of the issue's behavior and how it affects the OS: http://youtu.be/nfHydPRRxLQ

This bug occurs on Galaxy S and S II so far, but not on Galaxy Nexus (4.0.1). I will try today to reproduce it on other devices.

Comment 8

[Brad Lassey [:blassey] (use needinfo?)]

(In reply to Cristian Nicolae (:xti) from comment #7)
> Here is a video of the issue's behavior and how it affects the OS:
> http://youtu.be/nfHydPRRxLQ
> 
> This bug occurs on Galaxy S and S II so far, but not on Galaxy Nexus
> (4.0.1). I will try today to reproduce it on other devices.

Cristian, can you post a video of how you got into that state? That might help Naoki repoduce on his Galaxy S II.

Comment 9

[Cristian Nicolae (:xti)]

(In reply to Naoki Hirata :nhirata from comment #6)
> I can't seem to reproduce this on the Galaxy S II.  Will need to use the
> Captivate.

What Android version do you have on SII?

Comment 10

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

2.3.3

Comment 11

[JP Rosevear [:jpr]]

Chris, is this a dupe of the adreno lock up bug?

Comment 12

[Chris Lord [:cwiiis]]

(In reply to JP Rosevear [:jpr] from comment #11)
> Chris, is this a dupe of the adreno lock up bug?

This was reported prior to the Adreno lock-up, and happens on non-Adreno I think, so I guess not. Ccing Cristian for comment.

Comment 13

[Cristian Nicolae (:xti)]

(In reply to Brad Lassey [:blassey] from comment #8)
> (In reply to Cristian Nicolae (:xti) from comment #7)

> Cristian, can you post a video of how you got into that state? That might
> help Naoki repoduce on his Galaxy S II.

It seems that Fennec just freezes and flickers until a tap or a zoom action is performed on the latest Nightly on SII.

However, I tried to find a regression range using the Samsung Captivate:

- good maple build: 03/09
- bad maple build: 03/10

Possible regression range: http://hg.mozilla.org/projects/maple/pushloghtml?fromchange=c6dcca94622e&tochange=b4cc2666c7d5

Comment 14

[Cristian Nicolae (:xti)]

I tried to find some certain steps for this bug on the latest Nightly, and it seems to be something simple:

1. Open Fennec
2. Load http://www.kevs3d.co.uk/dev/
3. Pan/Zoom the page
4. Wait

On today's Nightly, after several minutes (5+), the device is totally locked. I have to pull out the battery. This behavior is exactly like for bug 740778. However the regression range for this bug is different then Adreno issue.

--
Firefox 14.0a1 (2012-04-10)
Device: Samsung Galaxy S (Captivate)
OS: Android 2.2

Comment 15

[JP Rosevear [:jpr]]

George, not sure we want to fix this yet, but can you diagnose the root cause?

Comment 16

[Cristian Nicolae (:xti)]

Note: The first thing that occur in this bug are those high composite values mentioned in comment #0:

I/Gecko   ( 3998): Compositor: Composite took 503 ms.
I/Gecko   ( 3998): Compositor: Composite took 559 ms.
I/Gecko   ( 3998): Compositor: Composite took 236 ms.
I/Gecko   ( 3998): Compositor: Composite took 285 ms.

The layout is shaking around when those values are triggered in console.

Comment 17

[JP Rosevear [:jpr]]

Interesting, could be related to bug 737801 or bug 743247

Comment 18

[Cristian Nicolae (:xti)]

The patch from Bug 743247, it seems that resolved this issue too. Closing bug as verified fixed on Samsung Captivate