1032693 - [dolphin]No response on homescreen, because there is a 'fadeout' but no'active' class in <div id=homescreen...>

Status: RESOLVED WONTFIX

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

Description

[yang.zhao]

Attachment: 'fadeout' but no 'active' for homescreen div

It appears occasionally, one is by manully,steps:
1,launch the contact app to do some operation
2,long press the home button to kill the contacts, but need to slide more than once to kill it
3,then there is no response when touch the homescreen.This means couldn't slide the homescreen and no response when clicking the app icons on homescreen

From the app-manager, there is a 'fadeout' class in "<div id='homescreen'...>",but no 'active' class.

Comment 1

[yang.zhao]

hi,James
   Please help to find someone to see this issue.Thank you.

Comment 2

[Wayne Chang [:wchang]]

Hi Evelyn,

Can you have someone check this one out?

Comment 3

[Rachelle Yang [:ryang][[e-mail]]]

Per Comment2, kindly ask for Evelyn's further analysis.Thanks!

Comment 4

[Evelyn Hung]

Luke, can you work with Alive to have a quick idea? Thanks.

Comment 5

[Wayne Chang [:wchang]]

Yang,

can you provide the STR for this and if this has also been reproduced on Flame?
We're a bit short on information here and it will be hard to move forward.

Comment 6

[yang.zhao]

(In reply to Wayne Chang [:wchang] from comment #5)
> Yang,
> 
> can you provide the STR for this and if this has also been reproduced on
> Flame?
> We're a bit short on information here and it will be hard to move forward.
Sorry,we don't have the STR. STEPS in comment 1 is what I did before the issue occurs, but only occurs once by now.Our QA also meet this issue after running monkey test.

Comment 7

[Luke Chang [:lchang] (inactive)]

So far, I can't reproduce this bug manually, either. I'll try putting some logs to dig more information.

Comment 8

[thomas tsai]

(In reply to yang.zhao from comment #6)
> (In reply to Wayne Chang [:wchang] from comment #5)
> > Yang,
> > 
> > can you provide the STR for this and if this has also been reproduced on
> > Flame?
> > We're a bit short on information here and it will be hard to move forward.
> Sorry,we don't have the STR. STEPS in comment 1 is what I did before the
> issue occurs, but only occurs once by now.Our QA also meet this issue after
> running monkey test.
It's once issue. Is it still necessary 1.4?

Comment 9

[thomas tsai]

(In reply to yang.zhao from comment #6)
> (In reply to Wayne Chang [:wchang] from comment #5)
> > Yang,
> > 
> > can you provide the STR for this and if this has also been reproduced on
> > Flame?
> > We're a bit short on information here and it will be hard to move forward.
> Sorry,we don't have the STR. STEPS in comment 1 is what I did before the
> issue occurs, but only occurs once by now.Our QA also meet this issue after
> running monkey test.
Hi Zhao: How often does it happen in QA monkey tests?

Comment 10

[yaoyao.wu]

(In reply to thomas tsai from comment #9)
> (In reply to yang.zhao from comment #6)
> > (In reply to Wayne Chang [:wchang] from comment #5)
> > > Yang,
> > > 
> > > can you provide the STR for this and if this has also been reproduced on
> > > Flame?
> > > We're a bit short on information here and it will be hard to move forward.
> > Sorry,we don't have the STR. STEPS in comment 1 is what I did before the
> > issue occurs, but only occurs once by now.Our QA also meet this issue after
> > running monkey test.
> Hi Zhao: How often does it happen in QA monkey tests
Hi thomas,

The probability is 1/8.

Comment 11

[Ivan Tsay (:ITsay)]

Hi Luke,

Mind if you take this blocker. Also, per your comment 7, can you provide a patch that can print more logs for our partner to reproduce it and collect the logs.

Comment 12

[Luke Chang [:lchang] (inactive)]

Hi Ivan,

Sure, here is the patch:
https://github.com/luke-chang/gaia/commit/8c76dec00af20ea7daf2d271a3cd614e8d9bead5.diff


Hi Yang,

Both Tzu-Lin and I think this bug may be similar to Bug 1031225. The patch above is the same as Tzu-Lin provided in that bug. Could you please help to apply this patch and get some logs after running monkey test again?

Thanks.

Comment 13

[Luke Chang [:lchang] (inactive)]

Hi Yang,

We've tried running monkey test many times but can't reproduce this issue at our side. I'd like to know if you have any idea. Thanks.

Comment 14

[yang.zhao]

I think maybe it's related with bug 1031225.Since the log patch you gave in comment 12 will print a lot of logs, I have asked Tzu-Lin to give me another log patch and wait for our QA to reproduce the issue.Maybe we can wait for the log to see if there is any information that could help.

@yaoyao It seems that sprd328761 reproduced yesterday, have you found any new information? Please comment here, thank you!

Comment 15

[yaoyao.wu]

(In reply to yang.zhao from comment #14)
> I think maybe it's related with bug 1031225.Since the log patch you gave in
> comment 12 will print a lot of logs, I have asked Tzu-Lin to give me another
> log patch and wait for our QA to reproduce the issue.Maybe we can wait for
> the log to see if there is any information that could help.
> 
> @yaoyao It seems that sprd328761 reproduced yesterday, have you found any
> new information? Please comment here, thank you!
Yes,the issue reproduced again yesterday.After running a long time monkey test, our tester long press the home button ,the issue reproduced.
The corresponding code is:
case 'cardviewbeforeshow':
          // Fade out the homescreen before showing the cards view to avoid
          // having it bleed through during the transition animation.
          this.getHomescreen().fadeOut();
          break;
The code leads to homescreen in "fadeout" .

Comment 16

[yaoyao.wu]

While trying to analysis the scene of bug 1031225 ,I reproduced the issue accidentally. Because both homescreen and Email are active ,so I use 

var childs = document.querySelectorAll("#windows .appWindow");
var appDiv = childs[1]; //child[1]refers to E-mail
appDiv.parentNode.removeChild(appDiv)

to get rid of the active Email app. After that the phone return to normal.
I try to enter Calendar app ,but the phone reacts slowly,so I long press the home button try to kill the app,after pressing the button ,the homescreen get into "fadeout".

Comment 17

[yang.zhao]

Attachment: 0-main-22-05-22.log.zip

hi,Luke
  Reproduce again! After running monkey test, the phone turns out to be slow but still normal, then launch several apps and long press home button to kill them, the issue occurs.
  The attachment is the main log with your log patch.

Comment 18

[Luke Chang [:lchang] (inactive)]

Hi Yang,

I still can't reproduce this issue with our latest gaia. I'm wondering which revision of gaia you're using for monkey test. Thanks.

Comment 19

[yang.zhao]

@yaoyao
   Please see comment#18 and tell Luke the revision of gaia. Thank you!

Comment 20

[Luke Chang [:lchang] (inactive)]

Seems we found a possible solution. Please refer to Bug 1031225 comment 23 and see if it can resolve all of these relevant bugs.

Comment 21

[Keven Kuo [:kkuo]]

Hi! Luke,

Any update?

--
Keven

Comment 22

[Luke Chang [:lchang] (inactive)]

Hi Yang,

Could you please confirm if the patch in Bug 1031225 comment 23 can resolve this issue or not? Thanks a lot.

Comment 23

[yang.zhao]

I'm not following the issue now,so add yaoyao to answer this question.

Comment 24

[yaoyao.wu]

(In reply to Luke Chang [:lchang] from comment #22)
> Hi Yang,
> 
> Could you please confirm if the patch in Bug 1031225 comment 23 can resolve
> this issue or not? Thanks a lot.
Hi Luke and Yang,
   The tester need more time to run monkey test to confirm. I'll test you the result as soon as the tester gives the result .

Comment 25

[yaoyao.wu]

(In reply to yaoyao.wu from comment #24)
> (In reply to Luke Chang [:lchang] from comment #22)
> > Hi Yang,
> > 
> > Could you please confirm if the patch in Bug 1031225 comment 23 can resolve
> > this issue or not? Thanks a lot.
> Hi Luke and Yang,
>    The tester need more time to run monkey test to confirm. I'll test you
> the result as soon as the tester gives the result .
Hi Luke and Yang,
     It seems that the patch in Bug 1031225 comment 23 can't resolve this issue.

Comment 26

[Rachelle Yang [:ryang][[e-mail]]]

Hi Luke, May you please kindly update any progress ? Thanks a lot.

Comment 27

[Luke Chang [:lchang] (inactive)]

Hi Rachelle and Yaoyao,

This issue still can't be reproduced at our side by neither hand nor monkey test. I need more time to figure it out and will update my progress here as soon as possible.

Comment 28

[Evelyn Hung]

[Blocking Requested - why for this release]:
Is it still a blocker?


Per comment 27, we need our QA's help to reproduce this issue on our monkey test.

Comment 29

[Cody Roesch [:croesch]]

This bug does NOT repro on: Flame 1.4

Actual Result: Following the STR in Comment 0, I'm unable to get this behaviour on the Flame device.

Repro Rate: 0/25

Environmental Variables:
Device: Flame 1.4
Build ID: 20140804033126
Gaia: 9377274b17200a60cebcd2427d489a7756c4cc72
Gecko: 93e736da9863
Version: 30.0 (1.4)
Firmware Version: v122

Comment 30

[Wayne Chang [:wchang]]

Unable to reproduce on flame/monkey.

minusing for now until further occurrences are seen.

Comment 31

[BMO Automation]

Firefox OS is not being worked on