913769 - [B2G][ Helix][Performance]The App Exit Time is too long when close the App

Status: RESOLVED INVALID

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

Description

[lecky]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E)

Steps to reproduce:

gaia：c0ea0a4943dc8d3751b07f5b5c5d3abe06364a14  
gecko：170f9e477571127cd40997fa2abe262ed43f0e4d  
gonk-misc：ca9192d7ef6037016d4723647d86b72f7a410633

【Repro Steps*】：
1.open the app in the table below
2.close app
3.record the exit time of each app 

Please check the test result in the attachment.

【Test Count*】：5
【Found Count*】：5

【Network environment】：NA

【Resume operation】：NA

Comment 1

[lecky]

Module	         Test Item	        Expect Test Result	Test Result	Real Test Result
Dailer	         Exit Dailer Time	300ms	                Failed	         390ms
Call History	 Exit Call History Time	300ms	                Failed	         700ms
Message	         Exit Message Time	300ms	                Failed	         467ms
Contacts	 Exit Contacts Time	300ms	                Failed	         690ms
Camera	         Exit Camera Time	300ms	                Failed	         972ms
Browser	         Exit Browser Time	300ms	                Failed	         746ms

Comment 2

[lecky]

Attachment: Bug 913769 .csv

Comment 3

[Wayne Chang [:wchang]]

Hi Lecky,

Can you file the bugs separately and nominate hd? for those that are actually considered blocking?
I took a look and all of the app exit times are less than 1s, although not meeting your requirement of 300ms but I believe majority are acceptable at this stage for v1.1

Comment 4

[Maria]

Bug marked as INVALID. We'll check it again and if we find significant differences between expected and actual result in Mozilla build, we'll open a new bug per each issue with the proper priority.

Sorry for the inconvenience.