Closed Bug 1133111 Opened 10 years ago Closed 9 years ago

Black screen when switching apps with edge gesture

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(b2g-v2.2 affected, b2g-master affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: sfoster, Unassigned)

References

Details

(Whiteboard: [systemsfe])

STR: 1. Open several apps 2. Use edge gesture to swipe back and forth between apps (may have to repeat several times, could be memory dependant?) Expected: we see the screenshot+icon for the swiped-in, then the app transitions to active Actual: Sometimes when transitioning the screenshot is replaced by a black screen I see nothing in the logcat for this, but turning on DEBUG in app_window.js, its clear this occurs when the incoming app has crashed. The swipein event is received, but the appwindow doesnt get revived and is left in a closed state.
Seems like at https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/app_window.js#L1886, the transitionController exists still, so we never reviveBrowser(). Not sure when that is supposed to get reset? Also, I'm not clear why there's nothing about this crash in the logcat? If its a memory pressure event, 1) why? I've only got a couple apps open. 2) shouldn't we see that in logcat?
(In reply to Sam Foster [:sfoster] from comment #1) > Seems like at > https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/app_window. > js#L1886, the transitionController exists still, so we never > reviveBrowser(). Not sure when that is supposed to get reset? Oh, misread. The browser crashed, transitionController still exists so we just return here. That seems wrong? It leaves the appwindow element visible like so: <div aria-hidden="true" loading-state="false" style="background-image: none; background-size: 120px 120px; width: 320px; height: 569.333px;" data-manifest-name="Music" class="appWindow render suspended" id="AppWindow_6" transition-state="closed"></div>
Blocks: 1139607
If we can repro this on master and 2.2 it should get nominated.
Keywords: qawanted
QA Contact: bzumwalt
Issue does reproduce on Flame 2.2 and 3.0 With Marketplace, Browser, Camera, Gallery, and Settings open edge gesturing between them produces occasional black screen that replaces expected screenshot. This all black screenshot usually disappears within a second or less. On one occasion browser that showed black screenshot suddenly killed itself. Video: http://youtu.be/iIVrRHoup1k Device: Flame 2.2 Build ID: 20150316002502 Gaia: a6b2d3f8478ec250beb49950fecbb8a16465ff6f Gecko: 18619f8f6c5c Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 Device: Flame 3.0 Build ID: 20150316010202 Gaia: 4868c56c0a3b7a1e51d55b24457e44a7709ea1ae Gecko: 436686833af0 Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b Version: 39.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
I'm not sure the video in #Comment 4 demonstrates the bug - the only black I see there is the expected black from the Camera. I've tried and failed to reproduce for the last 10mins on my 319MB flame (master)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: steps-wanted
QA Contact: bzumwalt
This issue is not reproducible on latest Flame 2.5 319MB. Currently we're seeing aggressive app killing in low memory setup like described in bug 1172167, so I couldn't have more than a few apps to be edge gesturing to/from. I think we can close this bug out. Device: Flame (full flashed, 319MB, KK) BuildID: 20150714010206 Gaia: 7676b68b4d32ed13243eeb719188847121bd5611 Gecko: 0931671a14ef Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5 Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: steps-wanted
What do you think Sam? We haven't seen this occur. Safe to close out at this point?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(sfoster)
(In reply to KTucker [:KTucker] from comment #7) > What do you think Sam? We haven't seen this occur. Safe to close out at this > point? Agreed, we can re-open if it pops up again, but I'm unable to reproduce this on current master/nightly
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(sfoster)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.