Closed
Bug 1282292
Opened 8 years ago
Closed 8 years ago
Blank white screen on launch
Categories
(Firefox for Android Graveyard :: Awesomescreen, defect, P1)
Tracking
(fennec50+)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
fennec | 50+ | --- |
People
(Reporter: bullionareboy, Assigned: snorp)
References
Details
(Keywords: nightly-community)
Attachments
(4 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20160625030241
Steps to reproduce:
Launch Nightly from app-drawer/home screen
Actual results:
Blank Screen
Nothing loads even after waiting sometime.
Expected results:
Awesome Screen should be displayed
Workaround:
Clear from recent apps or Force stop Nightly and launch again.
Another user:
https://www.reddit.com/r/firefox/comments/4pu3ap/nightly_for_android_constantly_freezing/
Moto G 2ng Gen MM
Keywords: nightly-community
Updated•8 years ago
|
tracking-fennec: --- → ?
Comment 1•8 years ago
|
||
Once the you get the "Nightly isn't responding" dialogue, it would be helpful the get the corresponding ANR trace to see where Firefox is hanging.
If anybody who's experiencing this has got a rooted device, simply running |adb pull /data/anr/traces.txt" should be enough, for non-rooted devices alternatively this (http://stackoverflow.com/a/37628501) might be working instead.
If you've got that file showing Firefox hanging, attach it to this bug.
(In reply to Jan Henning [:JanH] from comment #1)
> Once the you get the "Nightly isn't responding" dialogue, it would be
> helpful the get the corresponding ANR trace to see where Firefox is hanging.
>
> If anybody who's experiencing this has got a rooted device, simply running
> |adb pull /data/anr/traces.txt" should be enough, for non-rooted devices
> alternatively this (http://stackoverflow.com/a/37628501) might be working
> instead.
> If you've got that file showing Firefox hanging, attach it to this bug.
Havn't seen any "Nightly isn't responding" dialogs. Its just a plain white screen.
I didn't notice it on the 27/06/2016 build so far, will try see if i can get those commands working incase i encounter this again.
Comment 3•8 years ago
|
||
Ah, I had feared that some variety of bug 1279273 might have returned, but if it looks like a different sort of hang, then disregard my comment for the time being.
Hey i got the trace files but im not sure of the order - forgive me.
its my first try pulling off traces file and have no clue about it.
i got the nightly not responding dialog and not knowing what to do took one before hitting "ok" and another after hitting 'ok'
its hard to reproduce this bug.
attaching the before force close version first
Also got this crash report
Not sure if it's related https://crash-stats.mozilla.com/report/index/d5f744ae-e78b-4c5b-8ff8-842e62160629
Comment 7•8 years ago
|
||
Unfortunately, that ANR trace (those two files seem to be identical) seems to date from March last year.
:JanH
is it a mistake from my end regarding the ANR trace thing?
Also this is how the multitask switcher looks like when the problem occurs
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → snorp
tracking-fennec: ? → 50+
Updated•8 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P1
Updated•8 years ago
|
I think I have this same problem on aurora, but I don't think it's a hang but rather a rendering bug. When I coke back to Firefox Aurora after exiting but not killing it, there is a blank white space where the page should be, but the UI still works and the problem disappears when I switch tabs.
Comment 10•8 years ago
|
||
This is how it looks when I resume firefox after opening home screen or another app. UI is full-functional and normal behavior resumes if you switch tabs.
Comment 11•8 years ago
|
||
I can.confirm that this no longer happens now that aurora has gone to Firefox 52.
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•