1019419 - [dolphin]Can't back to homescreen from an app after running monkey test

Status: RESOLVED DUPLICATE of bug 1047645

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

Description

[yang.zhao]

Attachment: Screenshot of app-manager.png

After running gaia-test on dolphin for several hours ,the phone stays in an app ,press "Home" button can't make the phone return to idle.

One example is the phone stays on the calendar app,and can't back to homescreen.
From the app-manager,the 'calendar' and 'homescreen' are both active.When press the 'HOME' button,the code in app_window_manager.js went into the 'else' sentence,but in fact the calendar is in foreground:

case 'home':
          if (!HomescreenLauncher.ready)
            return;

          if (activeApp && !activeApp.isHomescreen) {
            // Make sure this happens before activity frame is removed.
            // Because we will be asked by a 'activity-done' event from gecko
            // to relaunch to activity caller, and this is the only way to
            // determine if we are going to homescreen or the original app.

            this.debug('back to home.');
            console.log("\nwei.gao_ApptoHome");
            this.display(HomescreenLauncher.origin);
          } else {
            // dispatch event to close activity.
            this.debug('ensure home.');
            HomescreenLauncher.getHomescreen().ensure(true);
          }
          break;

Comment 1

[yang.zhao]

hi,Alive
  Do you have any idea on this issue ?

Comment 2

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

No, and what's sad is I sometimes found this but without better STR. I will appreciate if you provide stable STR.

Comment 3

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

I will take this bug and put in a low priority queue now.

Comment 4

[yang.zhao]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #3)
> I will take this bug and put in a low priority queue now.
I don't have the STR ,but it's easy to reproduce when runing gaia-ui test

Comment 5

[yang.zhao]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #3)
> I will take this bug and put in a low priority queue now.
It reproduced on Dolphin with a high rate.
When this issue occurs,if I remove 'active' from the class of Appwindow div ,and change the transition-state from 'opened' to 'closed' from the app-manager,after I do the two things,the phone will become normal.So I guess maybe the app was wrong when doing the transition state.
Since it's easy to reproduce when running gaia-ui test,can you give me a patch with log for reproducing this?Thank you.

Comment 6

[James Zhang (Spreadtrum)]

Yang, can you try flame reference phone?

Comment 7

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

(In reply to yang.zhao from comment #5)
> (In reply to Alive Kuo [:alive][NEEDINFO!] from comment #3)
> > I will take this bug and put in a low priority queue now.
> It reproduced on Dolphin with a high rate.
> When this issue occurs,if I remove 'active' from the class of Appwindow div
> ,and change the transition-state from 'opened' to 'closed' from the
> app-manager,after I do the two things,the phone will become normal.So I
> guess maybe the app was wrong when doing the transition state.
> Since it's easy to reproduce when running gaia-ui test,can you give me a
> patch with log for reproducing this?Thank you.

I guess what you need is AppWindow.prototype._DEBUG = true

Comment 8

[yang.zhao]

./0-main-15-47-51.log:06-06 17:07:18.449  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2085.153] Handling _localized event...
./0-main-15-47-51.log:06-06 17:07:18.449  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2085.154] Handling _localized event...
./0-main-15-47-51.log:06-06 17:07:18.449  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2085.155] publishing internal event: namechanged
./0-main-15-47-51.log:06-06 17:07:18.449  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2085.156] publishing external event: namechanged
./0-main-15-47-51.log:06-06 17:07:25.596  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2092.519] publishing internal event: willdestroy
./0-main-15-47-51.log:06-06 17:07:25.596  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2092.520] publishing external event: willdestroy
./0-main-15-47-51.log:06-06 17:07:25.596  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2092.520] removing element... 
./0-main-15-47-51.log:06-06 17:07:25.596  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2092.521] publishing external event: destroyed
./0-main-15-47-51.log:06-06 17:07:25.596  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2092.522] publishing external event: terminated
./0-main-15-47-51.log:06-06 15:09:41.849  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.775] Handling mozbrowserloadstart event...
./0-main-15-47-51.log:06-06 15:09:41.849  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.775] Handling mozbrowserloadstart event...
./0-main-15-47-51.log:06-06 15:09:41.849  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.777] publishing internal event: loading
./0-main-15-47-51.log:06-06 15:09:41.849  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.777] publishing external event: loading
./0-main-15-47-51.log:06-06 15:09:41.979  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.902] Handling mozbrowsersecuritychange event...
./0-main-15-47-51.log:06-06 15:09:41.979  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.910] Handling mozbrowserlocationchange event...
./0-main-15-47-51.log:06-06 15:09:41.979  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.911] Handling mozbrowserlocationchange event...
./0-main-15-47-51.log:06-06 15:09:41.979  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.911] publishing internal event: locationchange
./0-main-15-47-51.log:06-06 15:09:41.979  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2228.911] publishing external event: locationchange

Sorry for couldn't find the STR ,I set AppWindow.prototype._DEBUG = true ,and the log above is the log with tag [Calendar],I found there is no 'closing' event before terminated .Does this may cause this issue ?

Comment 9

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

(In reply to yang.zhao from comment #8)
> Sorry for couldn't find the STR ,I set AppWindow.prototype._DEBUG = true
> ,and the log above is the log with tag [Calendar],I found there is no
> 'closing' event before terminated .Does this may cause this issue ?

Is Calendar foreground before terminating?
There will be no closing event if it's already at closed state.

Could you attach the full log? Thanks.

Comment 10

[yang.zhao]

Attachment: 0-main-15-47-51.log.zip

The attachment is the full log.
It seems that the Clock app is in foreground ,both the clock and calendar are all terminated,but the Clock app has 'closing' event while calendar doesn't.The log is also with [AppWindowManager] debug enabled.

Comment 11

[Preeti Raghunath(:Preeti)]

Please repro on device and we're backlog as it is not reproducible.

Comment 12

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

It's hard to say what happens according to the log.. if this issue occurs on real devices I will priority it. Sorry about that.

Comment 13

[yang.zhao]

./0-main-15-47-51.log:06-06 17:07:13.825  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2080.727] publishing external event: closed
./0-main-15-47-51.log:06-06 17:07:13.825  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2080.727] publishing internal event: close
./0-main-15-47-51.log:06-06 17:07:13.825  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2080.728] publishing external event: close

>here Calendar publish close event

./0-main-15-47-51.log:06-06 17:07:14.045  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Clock][2080.971] nextpainted.
./0-main-15-47-51.log:06-06 17:07:14.165  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.088]setVisible on browser element:false
./0-main-15-47-51.log:06-06 17:07:14.165  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.093] Handling mozbrowservisibilitychange event...
./0-main-15-47-51.log:06-06 17:07:14.165  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.093] Handling mozbrowservisibilitychange event...
./0-main-15-47-51.log:06-06 17:07:14.165  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.093] publishing internal event: background
./0-main-15-47-51.log:06-06 17:07:14.165  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.094] publishing external event: background

>here Calendar become background ,but the next Calendar begin loading

./0-main-15-47-51.log:06-06 17:07:15.016  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.938] Handling mozbrowserloadstart event...
./0-main-15-47-51.log:06-06 17:07:15.016  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.939] Handling mozbrowserloadstart event...
./0-main-15-47-51.log:06-06 17:07:15.016  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.940] publishing internal event: loading
./0-main-15-47-51.log:06-06 17:07:15.026  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2081.941] publishing external event: loading
./0-main-15-47-51.log:06-06 17:07:15.136  5408  5408 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:783 in aw_debug: [Dump: AppWindow][Calendar][2082.056] Handling mozbrowserlocationchange event...

Comment 14

[yang.zhao]

hi,alive
   Please see comment 13 ,is it correct if an app is in background ,but still could do 'loading' event?Thank you for your help.

Comment 15

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

(In reply to yang.zhao from comment #14)
> hi,alive
>    Please see comment 13 ,is it correct if an app is in background ,but
> still could do 'loading' event?Thank you for your help.

App could load anything in background unless they don't want.

Comment 16

[yang.zhao]

Sorry for bothering you again.This time the phone stays in E-mail app,and can't back to homescreen after running 20 minutes monkey test.

06-13 13:43:59.829   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][723.682] current is app://fm.gaiamobile.org; next is app://email.gaiamobile.org

> here begin change from fm to email,and this is email launched for the firt time

06-13 13:43:59.839   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][723.682][object Object]
06-13 13:43:59.839   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][723.684]app://email.gaiamobile.orgfalse
06-13 13:43:59.839   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][723.691]=== Active app now is: ,E-Mail,===

>here active app is e-mail

06-13 13:43:59.869   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][723.694]before ready check[object Object][object Object]
06-13 13:43:59.869   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][E-Mail][723.694]requesting to open
06-13 13:43:59.879   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][E-Mail][723.695]loaded yet

>here no changing from e-mail to fm ,but fm was opened ,then the active app is fm .

06-13 13:43:59.879   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.655]openApp has been ENDED!
06-13 13:43:59.879   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.661]opening,opened,::,complete
06-13 13:43:59.889   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.677] publishing internal event: opened
06-13 13:43:59.899   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.687]Dump: set visibility -> ,true
06-13 13:43:59.899   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.690]before showing frame
06-13 13:43:59.909   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.693]setVisible on browser element:true
06-13 13:43:59.909   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.708]screenshot state -> ,frame
06-13 13:43:59.909   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.719] locking screen orientation to default
06-13 13:43:59.919   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window.js:785 in aw_debug: [Dump: AppWindow][FM Radio][724.729] publishing external event: opened
06-13 13:43:59.919   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][724.744]app://fm.gaiamobile.orgfalse
06-13 13:43:59.919   834   834 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][724.756]=== Active app now is: ,FM Radio,===

Comment 17

[yang.zhao]

Attachment: can't_back_to_homescreen_from_E-mail.zip

Sorry for bothering again,please see the log in last comment.The attachment is the full log.Is it correct if active fm app just for 'animationend' event was received while the e-mail app has just active ?Thanks a lot!^_^

Comment 18

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

It seems impossible to go to email from fm. I guess monkey just quickly click the icon on homescreen randomly.

Comment 19

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

So the problem seems: the openApp animation is still ongoing even AWM switches fm to email.
More, the second app is launched during the first app is transitioning.

Don't know if human could reproduce this.

Comment 20

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

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #19)
> So the problem seems: the openApp animation is still ongoing even AWM
> switches fm to email.
> More, the second app is launched during the first app is transitioning.
> 
> Don't know if human could reproduce this.

Trying to reproduce this on flame v1.4: not reproducible. it's still able to back to homescreen.

Comment 21

[yang.zhao]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #19)
> So the problem seems: the openApp animation is still ongoing even AWM
> switches fm to email.
> More, the second app is launched during the first app is transitioning.
> 
> Don't know if human could reproduce this.

It's easy to reproduce when running monkey test.The following log is from a phone stays in Messages app after running monkey test.I searched the string |Active app now is: ,Messages,| in the log ,here is the last time the string appears:

06-14 17:46:12.701   842   842 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][29521.416]app://sms.gaiamobile.orgfalse
06-14 17:46:12.711   842   842 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][29521.417]=== Active app now is: ,Messages,===
>here Messages is active ,but imeadiatelly seems that this._updateActiveApp in AWM excuted again ,and Contacts became the active app.
06-14 17:46:12.711   842   842 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][29522.180]app://communications.gaiamobile.org/con        tacts/index.htmlfalse
06-14 17:46:12.731   842   842 E GeckoConsole: Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][29522.181]=== Active app now is: ,Contacts,===

Comment 22

[yang.zhao]

Can you run monkey test on dolphin ?Since it is very easy to reproduce on our side when running monkey test .Thank you.

Comment 23

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

I am not told we need to fix all monkey test issues.
Also if you don't convince this is reproducible by human, any fix could not be landed to v1.4 since you don't have another v1.4d branch.

Please help to find out someone else to dedicate on this bug if this one is valuable. I am already blocked by lots of 1.4/2.0 blockers.

Comment 24

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

Please take this bug to 1.4+ if this is a release blocker. Thanks.

Comment 25

[yang.zhao]

I am able to reproduce it by clicking the home button and apps randomly and quickly.The phone stays on Usage app,the log here is:

E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.654]launchingapp://gallery.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.655]displaying app://gallery.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.655] current is homescreen; next is app://gallery.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.655][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.656]app://gallery.gaiamobile.orgtrue
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.656]=== Active app now is: ,Gallery,===
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10317.657]before ready check[object Object][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.498]launchingapp://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.498]displaying app://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.498] current is app://gallery.gaiamobile.org; next is app://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.499][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.506]app://costcontrol.gaiamobile.orgfalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.506]=== Active app now is: ,Usage,===
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.507]before ready check[object Object][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10318.801]ready to open/closefalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.135]launchingapp://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.136]displaying app://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.136] current is app://costcontrol.gaiamobile.org; next is app://costcontrol.gaiamobile.org
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.289]app://gallery.gaiamobile.orgtrue
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.294]=== Active app now is: ,Gallery,===
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.585]back to home.
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.585]displaying homescreen
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.585] current is app://gallery.gaiamobile.org; next is homescreen
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.585][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.586]homescreenfalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.587]=== Active app now is: ,Homescreen,===
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.587]before ready check[object Object][object Object]
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10319.685]ensure home.
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10320.254]ready to open/closetrue
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10320.393]app://costcontrol.gaiamobile.orgfalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10320.393]=== Active app now is: ,Usage,===
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10321.311]ready to open/closefalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10321.612]homescreenfalse
E/GeckoConsole(  108): Content JS LOG at app://system.gaiamobile.org/js/app_window_manager.js:502 in awm_debug: [AppWindowManager][10321.618]=== Active app now is: ,Homescreen,===

Comment 26

[yang.zhao]

From the log in comment 25 ,you could see that the sequence of event handler is like this:
->Gallery launchapp
->Usage launchapp
->Usage launchapp
->Gallery appopened 
->Gallery back to homescreen
->Usage appopened
->homescreen homescreenopened

So both of the Homescreen and Usage are 'active',the phone stays in Usage app.
The 'launchapp' and 'appopened/homescreenopened' events in different apps appear alternatively.And the same in attachement log can't_back_to_homescreen_from_E-mail.zip .

Comment 27

[James Zhang (Spreadtrum)]

(In reply to yang.zhao from comment #26)
> From the log in comment 25 ,you could see that the sequence of event handler
> is like this:
> ->Gallery launchapp
> ->Usage launchapp
> ->Usage launchapp
> ->Gallery appopened 
> ->Gallery back to homescreen
> ->Usage appopened
> ->homescreen homescreenopened
> 
> So both of the Homescreen and Usage are 'active',the phone stays in Usage
> app.
> The 'launchapp' and 'appopened/homescreenopened' events in different apps
> appear alternatively.And the same in attachement log
> can't_back_to_homescreen_from_E-mail.zip .

We have the reproduction path, I think 1.4+ is better.
Because when this issue happen, user can't do anything unless plug out the battery.

Comment 28

[Jan Jongboom [:janjongboom] (inactive)]

Attachment: Workaround

So I don't know where this actually happens, but this would be a workaround for humans. When we are on homescreen but there are multiple apps active for some reason, close immediate all other apps when pressing homescreen again.

Let me know if this is an acceptable workaround or reassign to a homescreen peer.

Comment 29

[bhavana bajaj [:bajaj]]

We need to know if this is reproducible on flame which his missing information here. james can you help ?

Comment 30

[yang.zhao]

(In reply to bhavana bajaj [:bajaj] from comment #29)
> We need to know if this is reproducible on flame which his missing
> information here. james can you help ?
Sorry for don't have the STR ,but if you click quickly on the app icons and home button at the same time,this issue maybe happen ,that because both 'launchapp' and 'appopened' events could invoke function |_updateActiveApp| in AppWindowManager ,but the event callback is asynchronous ,so if the event callback order appears like comment #26 ,this issue will occur.

Comment 31

[Jason Smith [:jsmith]]

Anything monkey test based we can't do QA analysis on. We'll need the partner to check this.

Comment 32

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

(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #28)
> Created attachment 8441435 [details] [review]
> Workaround
> 
> So I don't know where this actually happens, but this would be a workaround
> for humans. When we are on homescreen but there are multiple apps active for
> some reason, close immediate all other apps when pressing homescreen again.
> 
> Let me know if this is an acceptable workaround or reassign to a homescreen
> peer.

homescreen 'app' peer knows nothing about this.

Comment 33

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

Comment on attachment 8441435 [details] [review]
Workaround

The workaround makes sense but it depends how bad this bug is.
IMO we need to find out
(1) Does this impact the user?
(2) What's the operation to trigger this case?
Otherwise we are stacking up workarounds.

If this bug is in the long run 1.4+, please add unit tests for it, add a console.warn for us to know what's the app name who is active when homescreen is active and ask review again.

Comment 34

[yang.zhao]

(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #28)
> Created attachment 8441435 [details] [review]
> Workaround
> 
> So I don't know where this actually happens, but this would be a workaround
> for humans. When we are on homescreen but there are multiple apps active for
> some reason, close immediate all other apps when pressing homescreen again.
> 
> Let me know if this is an acceptable workaround or reassign to a homescreen
> peer.
I landed with a patch on our build ,let's wait for the result.

Comment 35

[Preeti Raghunath(:Preeti)]

Wayne,

This seems to be in the vendor build. Please confirm the same.

Comment 36

[yang.zhao]

(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #28)
> Created attachment 8441435 [details] [review]
> Workaround
> 
> So I don't know where this actually happens, but this would be a workaround
> for humans. When we are on homescreen but there are multiple apps active for
> some reason, close immediate all other apps when pressing homescreen again.
> 
> Let me know if this is an acceptable workaround or reassign to a homescreen
> peer.
Hi,Jan Jongboom
   The workround did work for this issue, but there is another issue.
   This issue here is the app is still alive,but there are two active appwindow div, 
   Now we meet other issue:the app is killed by LMK or other reasons, but the appwindow div is still in 'active' state and doesn't be removed. Please see bug 1031225 for more detail.Thank you!

Comment 37

[Preeti Raghunath(:Preeti)]

Backlog as the issue seems to be in the vendor build. Partners please continue to triage and fix this won't be in Moz 1.4 build but can proceed to completion on your repos.

Comment 38

[yang.zhao]

Attachment: WIP_v2

hi,Jan
   Please see comment #36,I added more based on your patch.Could you help to review it?Thank you!

Comment 39

[yaoyao.wu]

(In reply to Alive Kuo [:alive][NEEDINFO!] from comment #33)
> Comment on attachment 8441435 [details] [review]
> Workaround
> 
> The workaround makes sense but it depends how bad this bug is.
> IMO we need to find out
> (1) Does this impact the user?
> (2) What's the operation to trigger this case?
> Otherwise we are stacking up workarounds.
> 
> If this bug is in the long run 1.4+, please add unit tests for it, add a
> console.warn for us to know what's the app name who is active when
> homescreen is active and ask review again.

Hi Alive,

   A similar problem appears in our recent test, can't back to homescrren from Email app after running monkey test.But there is some difference:
1 |adb shell b2g-ps|: you'll see both Email and homescreen app pid
2 from the app-manager in system app, you'll see that both homescreen and Email are "active render"
3 But in nightly, the result of window.AppWindowManager.runningApps is :
Object { homescreen: Object, app://browser.gaiamobile.org: Object },there is no Email app.
  It's confusing that the result of window.AppWindowManager.runningApps is different from  app-manager and |adb shell b2g-ps|.

 Thanks.

Comment 40

[Jan Jongboom [:janjongboom] (inactive)]

Comment on attachment 8453697 [details] [diff] [review]
WIP_v2

Redirecting to system peer

Comment 41

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

Comment on attachment 8453697 [details] [diff] [review]
WIP_v2

Review of attachment 8453697 [details] [diff] [review]:
-----------------------------------------------------------------

Not knowing what is decided here, and since I am not told I should grant any patch of dolphin just like tarako..

* Code patterns. Lots lint errors.
* Don't define function inside a function. Move it out.
* No tests.
* Please find out the root cause of the existence of the so-called invalid window instances.
  If you feel you have difficulty then protome the priority of this bug and PM will find someone in mozilla to work on it.

Comment 42

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

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1019419#c37 I don't think you need to put your patch in our repo. But if you find out the root cause you are welcome to do.

Comment 43

[yang.zhao]

(In reply to Alive Kuo [:alive][NEEDINFO!][Berlin 7/14-7/18] from comment #42)
> According to https://bugzilla.mozilla.org/show_bug.cgi?id=1019419#c37 I
> don't think you need to put your patch in our repo. But if you find out the
> root cause you are welcome to do.
It's just a workaround,but now we'll try the patch in bug 1037041 first.
So you could just ignore the WIP_v2 here.Sorry to bother you.
You could see https://bugzilla.mozilla.org/show_bug.cgi?id=1031225#c23 for more detail.Thank you!

Comment 44

[James Zhang (Spreadtrum)]

[Blocking Requested - why for this release]:flame also has this issue. see bug 1045980

Comment 45

[Kevin Grandon :kgrandon]

Also the same issue as bug 1047645. Taking.