Device: flame Memory: 273MB Gaia 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/c6f9f0396153 BuildID 20140720160208 Version 32.0a2 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 STR: Setup MTBF test Test suite including keyboard, sms, music Randomly run automation test cases for about 2~6 hours. EXPECT: Homescreen can be showed correctly ACTUAL: foreground app was still active as figure. System tray still worked. Homescreen scrollable but can't launch other app.

Phone is on you desk with log enabled. Some thoughts: * Keyboard seems being hidden/removed for some reason but it shouldn't be (in process). * AppWindowManager actvie app is home when this bug occurs. Not sure what happens but deserves investigating. Lemme know if you have time to investigate. Not a blocker now but if this happens in 319MB we will need to fix.

update debug log

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #3) > Phone is on you desk with log enabled. > Some thoughts: > * Keyboard seems being hidden/removed for some reason but it shouldn't be > (in process). > * AppWindowManager actvie app is home when this bug occurs. > > Not sure what happens but deserves investigating. Lemme know if you have > time to investigate. Not a blocker now but if this happens in 319MB we will > need to fix. It should be a blocker since we can see it on even 512MB device, but not often. Strongly recommend to fix because it make test and real user blocked, and need to reboot eventually.

Attach post test run logcat

Update logcat

Hang at 17:11 48 minutes in the video https://vreplay.mozilla.com/replay/showRecordingExternal.html?key=kcf4uB9BAUOQU13

(In reply to Paul Yang [: pyang] from comment #5) > (In reply to Alive Kuo [:alive][NEEDINFO!] from comment #3) > > Phone is on you desk with log enabled. > > Some thoughts: > > * Keyboard seems being hidden/removed for some reason but it shouldn't be > > (in process). > > * AppWindowManager actvie app is home when this bug occurs. > > > > Not sure what happens but deserves investigating. Lemme know if you have > > time to investigate. Not a blocker now but if this happens in 319MB we will > > need to fix. > > It should be a blocker since we can see it on even 512MB device, but not > often. > Strongly recommend to fix because it make test and real user blocked, and > need to reboot eventually. Paul - If you think this is a blocker, can you nom it for 2.0?

(In reply to Paul Yang [: pyang] from comment #8) > Hang at 17:11 > 48 minutes in the video > https://vreplay.mozilla.com/replay/showRecordingExternal. > html?key=kcf4uB9BAUOQU13 this video at 15:11 looks like, homescreen is already launched, but takes longer time to load all icons. It may not be mgmt's issue.

I found an easy STR, 1. launch keyboard (I tested in uitest app) 2. press home and |adb shell kill HOME_PROCESS_ID|

[Blocking Requested - why for this release]: block v2.0 mtbf test currently

Hi Alive, this patch should fix the bug as I described in my STR. I think we've already _updateActiveApp in switchApp, so we don't need to do it in display.

PR to master same issue on master.

Comment on attachment 8463771 [details] PR to master r+ with nits on github, please pay attention before merging. Thanks for digging this. The other way to fix this.element null issue might be using app suspending mechanism in homescreenWindow by default then we will always have this.element. That is bug 1039203.

Thanks Alive, I still keep original solution but I will dig into bug 1039203. master, https://github.com/mozilla-b2g/gaia/commit/cc5af5e8130ad81fda59b49d8213fbd67e1a0ddd

This still happen in 20140728 pvt build as I ran through it with 319MB. I will make sure it is okay next build run.

v2.0: https://github.com/mozilla-b2g/gaia/commit/e8425788e0372fbbcc40387b799f0636c041fc14

I haven't seen any similiar issue in this round of MTBF (8 devices). I will temporarily marked it as verified fixed. thanks.