[Gallery] displays a white screen after call end and then goes back and shows previous fullscreen image

NEW
Unassigned

Status

Firefox OS
Gaia::Gallery
--
critical
5 years ago
5 years ago

People

(Reporter: Leo, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(blocking-b2g:-, b2g18+)

Details

(Reporter)

Description

5 years ago
1. Title : When we view image in full screen and receive-end call,White screen is displayed for some time then displays fullscreen image
2. Precondition : one image is needed in gallery
3. Tester's Action : Gallery-> selectimage ->full screen view ->recieve a incoming call->end call
4. Detailed Symptom (ENG.) : a white blank screen is displayed after call end and then displays back the fullscreen image
5. Gaia Revision #:  "d8036b7244d5d3d34d65099722b3aefbfb6f50a8"
6. Expected : 
7.Reproducibility: Y
1)Frequency Rate : 100%
8.Comparison Results : 
	1)Model Comparing : 
9. Attached files: 
	1)Log : 
	2)Test Contents : 
	3)Video file :
(Reporter)

Updated

5 years ago
blocking-b2g: --- → leo?

Updated

5 years ago
blocking-b2g: leo? → -
tracking-b2g18: --- → +

Comment 1

5 years ago
I was able to reproduce this as well. The white screen displayed after hanging up the call.

Unagi 
Build ID: 20130501070205
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/765d296cff66
Gaia: e420d71c9528786621f176fb4ce67d291e0a530e
Assignee: nobody → mbudzynski
Whiteboard: u=fx-os-user c=may-6-17 p=0
Whiteboard: u=fx-os-user c=may-6-17 p=0 → u=fx-os-user c=may-6-17 p=1
Could this be caused by the changes in bug 862970 (or in the bugs related to that one)?  That is when an incoming call occurs, it causes memory pressure and the image displayed by the gallery is flushed.  Then, when the dialer goes away, we're left with a white void until the image is decoded again?

I wonder if we could modify things to leave a black void instead of a white void, at least...

Setting needinfo for Justin and Joe to see if they have thoughts here.
Flags: needinfo?(justin.lebar+bug)
Flags: needinfo?(joe)
> Could this be caused by the changes in bug 862970 (or in the bugs related to that one)?  

Could be.  You can see memory-pressure events in the log.

> I wonder if we could modify things to leave a black void instead of a white void, at least...

That would be better!
Flags: needinfo?(justin.lebar+bug)
(In reply to Justin Lebar [:jlebar] from comment #3)
> > Could this be caused by the changes in bug 862970 (or in the bugs related to that one)?  

Oh, actually, I think we will throw out all of an app's images when it goes into the bg.  (We simulate memory pressure at that point in time.)

This is behaving as desired.  It's very hard to differentiate between this case, when we don't want to throw away the image, and a situation when we really do.  :-/
You could fix the white background by setting the background-color: of the img element (or div or whatever) to black. Short of not firing the memory pressure event when an app goes in the background, I don't know what we can do about this.
Flags: needinfo?(joe)
(In reply to Joe Drew (:JOEDREW! \o/) from comment #5)
> You could fix the white background by setting the background-color: of the
> img element (or div or whatever) to black. Short of not firing the memory
> pressure event when an app goes in the background, I don't know what we can
> do about this.

That would be a super-easy fix if so!  Thanks!

Michal: Bug 866174 removed background-color:black on the body element for gallery.  You could see if putting that back fixes this bug, and if so, talk to Vivien about the regression and how best to fix it.
That was one of the first things I've checked, unfortunately it doesn't fix the bug at all. It looks like the problem is on a platform side, not gaia.
Assignee: mbudzynski → nobody
Whiteboard: u=fx-os-user c=may-6-17 p=1
You need to log in before you can comment on or make changes to this bug.