1017536 - WindowManager gets broken after a while

Status: RESOLVED FIXED

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

Description

[:gerard-majax]

Reproducing this easily with current master on Nexus S at least.
Logcat shows this everytime I long press the home button:
> E/GeckoConsole(   77): [JavaScript Error: "TypeError: top.browser is null" {file: "app://system.gaiamobile.org/js/app_window.js" line: 1717}]
> E/GeckoConsole(   77): Content JS WARN at app://system.gaiamobile.org/js/app_window_manager.js:102 in awm_display: the app has been displayed.

STR for now:
 0. Boot device
 1. Launch a couple of apps
 2. Launch HERE Maps, let it run for a while

Please note I have been reproducing this since at least a week, maybe more. I can trigger it with other apps, too.

I suspect it may be because of OOM or something like this at some point. It's quite bothering, since you cannot anymore:
 - switch between apps (either task switcher or edge gestures)
 - if you lock the device with one app started, you cannot unlock until you tap twice on the home button

I'll try to reproduce this on Flame also, but I think I did at some point.

Comment 1

[:gerard-majax]

I could reproduce on Flame configured with 1GB after opening a lot of apps and switching between those.

Comment 2

[:gerard-majax]

Configuring Flame with 256MB the reproductibility is quite fast.

Comment 3

[Jason Smith [:jsmith]]

I see the STR here, but I don't understand what the expected/actual results are. Can you clarify?

What's needed for QA testing here also? Looks like you can reproduce on Flame, so we know this is present on a production device.

Comment 4

[:gerard-majax]

There are STRs and expected/actual in comment 1. I should have made it obvious that:

 Expected:
  Window Manager works, we can use edge gestures and tasks switcher

 Actual:
  Unable to switch between apps either with task switcher or edges gestures. This also messes up with locking the device: one need to tap on the home button several times before being able to unlock the device.

Comment 5

[Jason Smith [:jsmith]]

Okay - can we confirm this works as expected on 1.4?

Comment 6

[(inactive after 6/18) Alive Kuo [:alive]]

Attachment: https://github.com/mozilla-b2g/gaia/pull/19803/files

Well, I don't have a flame. Could you test with this?

Comment 7

[:gerard-majax]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #6)
> Created attachment 8431305 [details]
> https://github.com/mozilla-b2g/gaia/pull/19803/files
> 
> Well, I don't have a flame. Could you test with this?

Alive, Flame isn't needed, I'm reproducing this on nearly all my devices. It seems to be linked with amount of RAM and use in time.

Comment 8

[:gerard-majax]

Comment on attachment 8431305 [details]
https://github.com/mozilla-b2g/gaia/pull/19803/files

That seems to be helping!

Comment 9

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Triage: block based on user impact and low risk of the patch.

Comment 10

[(inactive after 6/18) Alive Kuo [:alive]]

https://github.com/mozilla-b2g/gaia/pull/19803