Closed Bug 1379612 Opened 7 years ago Closed 6 years ago

opening google docs page crashes and freezes device on fennec stable, beta and nightly

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(fennec?, firefox54 wontfix, firefox55 fix-optional, firefox56 fix-optional)

RESOLVED INACTIVE
Tracking Status
fennec ? ---
firefox54 --- wontfix
firefox55 --- fix-optional
firefox56 --- fix-optional

People

(Reporter: vihsaaa, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 5.1; Mobile; rv:56.0) Gecko/56.0 Firefox/56.0
Build ID: 20170708150130

Steps to reproduce:

open Manadsrapport-1760.xlt<https://docs.google.com/file/d/0B4qz_rnI8G9jVG5qeDM5Wmc5Qkk/edit?usp=drive_web>
wait for the doc to load
after a minute fennec closes or crashes before  loading the doc.
unable to use home and back  button on device
disabled all addons before opening the docs link


Actual results:

it closes the fennec and freezes the device. i have to power off the device.


Expected results:

load the document

device: lyf flame 3 [ ls-4001 ]
os: android 5.1

repro:
fennec 54.0.1 en-gb
fennec 55.0b5 en-us
fennec 56.0a1 20170708150130 en-gb
NI-ing myself to not forget to look over this
tracking-fennec: --- → ?
Flags: needinfo?(bogdan.surd)
OS: Unspecified → Android
Hardware: Unspecified → ARM
Version: unspecified → Trunk
Devices:
 - Nexus 6 (Android 7.0);
 - Huawei MediaPad M2 (Android 5.1.1).

Hello,

 I've tried to reproduce this issue on the above mentioned devices using the latest builds for Nightly, Beta and Release, I did use the en-gb and en-us versions that you mentioned for each of them. The browsers didn't freeze or crash. Sadly we do not have any flame devices on hand.
Flags: needinfo?(bogdan.surd)
Closing per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Contact :susheel if you think this bug should be re-opened
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.