Closed Bug 772139 Opened 12 years ago Closed 1 year ago

loading articles on the Economist sometimes reboots my phone

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
ARM
Android
Type:
defect

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: dbaron, Unassigned)

Details

Loading an article on the Economist's Web site sometimes reboots my phone.

I suspect (though I'm not certain) that it's related to the appearance of the fixed-positioned popup that shows up at the bottom of the page, but only shows up sometimes.  I suspect this because the time that the phone reboots seems to correspond to when the popup would show up on a desktop browser, about 10 seconds after the article loads.  (A little more data on that popup:  if, on desktop, I load http://t.co/NymK6dhJ in a clean profile, then reload a few times, I see no popup on the first load, the full animated popup only on the second load, and just the top tab of it on the third and later loads.)

My phone is a Morotola Triumph.

Steps to reproduce: load http://t.co/NymK6dhJ in Firefox for Android (nightly)

Actual results: after about 10 seconds, phone freezes and then reboots a second or two later

Expected results: no reboot
(In reply to David Baron [:dbaron] from comment #0)

What version of Android are you running?
Does setting webgl.disabled=true fix it?

A while ago we had similar trouble with The Economist as it used an old version of modernizr.js that was creating a WebGL context. See Bug 616416.
(That was with **** X11 drivers. Was not aware of similar issues on mobile devices.)
Testing if disabling webgl fixes it is a good idea; if that's the case, we should still figure out why.  You may want to run adb logcat and grab the output as you do this, to see if something shows up in the logs before the reboot happens as well.

(Another thing to test would be to just go to http://get.webgl.org/ and see if that reboots :)
This feels a lot like bug 757920
(In reply to Vladimir Vukicevic [:vlad] [:vladv] from comment #5)
> (Another thing to test would be to just go to http://get.webgl.org/ and see
> if that reboots :)

It doesn't.  It says "Hmm.  While your browser seems to support WebGL, it is disabled or unavailable.  If possible, please ensure that you are running the litest drivers for your video card."


(Also, since articles on the Economist only make the phone reboot some of the time, it's hard to verify things with that test.  That said, I've also seen things like loading large images make the phone reboot... enough that I tend to avoid loading anything with large images on my phone.)
Hrm.  Only 512MB on that device, is this just some failure of Froyo (or Moto devices in general) to handle OOM gracefully?  I've definitely seen some OOM-reboots on my Atrix even with gingerbread.
(In reply to David Baron [:dbaron] from comment #0)
> (nightly)
> 
> Actual results: after about 10 seconds, phone freezes and then reboots a
> second or two later


When it freezes you should be able to 'adb shell' into the phone. If you can post the results of dmesg that would be very useful.
(In reply to David Baron [:dbaron] from comment #7)
> (In reply to Vladimir Vukicevic [:vlad] [:vladv] from comment #5)
> > (Another thing to test would be to just go to http://get.webgl.org/ and see
> > if that reboots :)
> 
> It doesn't.  It says "Hmm.  While your browser seems to support WebGL, it is
> disabled or unavailable.  If possible, please ensure that you are running
> the litest drivers for your video card."

That means that WebGL context creation failed. The typical reason for this would be a blacklisted drivers, and the only drivers that we blacklist for WebGl on Android are certain Adreno drivers. 

Assuming that your build is recent enough to have the patches from bug 766251, it would be interesting to see your about:support graphics section.

Also, while this almost certainly excludes that WebGL might have anything to do with the reboot, it would still be useful to check if webgl.disabled=true fixes the reboot on economist.com
(In reply to Benoit Jacob [:bjacob] from comment #10)
> Assuming that your build is recent enough to have the patches from bug
> 766251, it would be interesting to see your about:support graphics section.

Graphics
Adapter Description     Qualcomm -- Adreno 205 -- OpenGL ES 2.0 1403843 --
Model: MOTWX435KT, Product: Caymus_VRGUS, Manufacturer: Motorola, Hardware: qcom
Vendor ID       Qualcomm
Device ID       Adreno 205
Driver Version  OpenGL ES 2.0 1403843
WebGL Renderer  Blocked for your graphics card because of unresolved driver
issues.
GPU Accelerated Windows 0
AzureBackend    skia
Thanks, there you go, "Adreno 205" here is one of the two renderer strings that are blacklisted for WebGL on Android. So, WebGL seems not to be the issue here.
For the record, still happens in 2012-09-23 nightly.
Severity: normal → S3

David, are you still experiencing this issue?

Flags: needinfo?(dbaron)

No, but I haven't used that phone since October 2013 (at the latest, maybe earlier).

Flags: needinfo?(dbaron)

Welp, Android 2.0 is unsupported nowadays so I suppose we can close this.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.