All users were logged out of Bugzilla on October 13th, 2018

Black screen flashes after minimizing and restoring the browser. (Xperia c3 device )

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
3 years ago
2 months ago

People

(Reporter: swapnildoiphode2, Assigned: droeh, NeedInfo)

Tracking

46 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Linux; Android 5.1.1; D2502 Build/19.4.A.0.182) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.83 Mobile Safari/537.36
Firefox for Android

Steps to reproduce:

1.Launch mozilla. 
2.Open multiple tabs by tapping on '+' button. (approximately 60)
3.Now open Google search page. 
4.Minimize and restore the browser. 
5.Observe that black screen flashes. 


Actual results:

Black screen flashes after minimizing and restoring the browser. 


Expected results:

Page should be clearly visible to the user without having any black screen issues.
(Reporter)

Comment 1

3 years ago
Please let me know if you require any more  regarding above issue.

Updated

3 years ago
Component: Untriaged → Graphics
Product: Firefox → Core
(Reporter)

Comment 2

3 years ago
@YF will you fix this issue?
Component: Graphics → Graphics, Panning and Zooming
Product: Core → Firefox for Android
Jamie, can you reproduce this?
Flags: needinfo?(jnicol)
(Reporter)

Comment 4

3 years ago
@jeff check this issue with 2G/3G network.
Yes I can reproduce some of the time, I'll have a look into it.
Flags: needinfo?(jnicol)
I am fairly certain this is not a graphics problem. We correctly composite immediately when SurfaceListener.surfaceChanged() is called in LayerView.java. Which happens when the activity is resumed, as expected.

The problem, however, appears to be that there is sometimes a delay between the user clicking to restore the app and the activity actually being resumed, during which time the app is black. I've not worked out why this is, or exactly how to reproduce 100% of the time. But having many tabs open makes it more likely, as does running a debug build.

Interestingly this line appears in the logcat immediately before the activity is resumed:

> 05-17 10:26:00.370   900  2982 I ActivityManager: Activity reported stop, but no longer stopping: ActivityRecord{ace62f6 u0 org.mozilla.fennec_jamie/org.mozilla.gecko.BrowserApp t70}

Snorp, is there somebody in the mobile team who would be able to look into this?
Flags: needinfo?(snorp)
Yeah, we can look at it. My gut feeling is that we are doing some work in Activity.onPause() that is still ongoing if you quickly try to resume, hence the delay. Dylan is messing with surface lifetime stuff right now, so I'll assign this to him.
Assignee: nobody → droeh
Flags: needinfo?(snorp)

Comment 8

2 months ago
Hi,

I was not able to reproduce the issue.

Tested with:
Browser / Version: Firefox Mobile Nightly 63.0a1 (2018-08-07)
Operating System: Sony Xperia Z5 Premium (Android 6.0.1)

Could you download the latest Nightly and retry?

Thank you!
Flags: needinfo?(swapnildoiphode2)

Comment 9

2 months ago
Due to the lack of additional info, I'll close this issue as Incomplete. If someone can provide more information please feel free to reopen the issue, thanks.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.