1150798 - [FFOS7715 v2.1]Settings] Failed to use options of Settings

Status: VERIFIED FIXED

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

Description

[Chaochao Huang]

Attachment: 0-main-21-26-32.log

STR：
1、Open the Settings app. 
2、Select any option from Settings.

OBSERVED:
3. Failed to use options of Settings.

EXPECTED:
4. Use options of Settings normally.

Comment 1

[Chaochao Huang]

Hi gasolin,

Could you help check this issue?

You can get a video about this issue from http://pan.baidu.com/s/1bnvsD4r .

Thanks.

Comment 2

[Chaochao Huang]

From the log:

04-02 21:54:17.830  1012  1012 E GeckoConsole: [JavaScript Error: "Error: Timeout for modules: " {file: "app://settings.gaiamobile.org/js/vendor/alameda.js" line: 1}]

I think some reason leads to load alameda.js unsuccessfully. Then failed to use options of Settings.

Comment 3

[Chaochao Huang]

Hi Vance,

I think this is a serious problem. Could you help look for someone to check this issue?

Thanks.

Comment 4

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Chaochao -

Is this bug 100% reproducible? if not, what is the reproducible rate? Also is there any possible RST that might cause this issue?

Thanks

Comment 5

[Chaochao Huang]

(In reply to Vance Chen [:vchen][[e-mail]] from comment #4)
> Hi Chaochao -
> 
> Is this bug 100% reproducible? if not, what is the reproducible rate? Also
> is there any possible RST that might cause this issue?
> 

The reproduction rate is very low. There isnot specific RST that might cause this issue. First analysis it according to the offered log.

Comment 6

[Chaochao Huang]

Hi Arthur,

Could you help check this problem?

From Log, loading alameda.js unsuccessfully leads to this problem. Why is it so？

Comment 7

[Chaochao Huang]

Hi Vance,

This is a VERY serious problem. Could you help look for someone to check this issue?

Thanks.

Comment 8

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi ChaoChao -

I totally agree that once reproduced, this issue is a very serious issue, however, as you mentioned on Comment#5, the reproduce rate is quite low. So the low reproduce rate combined with no RST, the best we can do is to investigate and guess from the log we have. And to be honest there is not much information within the log. So I am afraid we probably cannot make much progress on this one. Please understand the difficulties here

Thanks

Comment 9

[Arthur Chen [:arthurcc][inactive after 6/30]]

Normally loading alameda.js won't fail. There might be racing in gecko but there is not much information in the log. We may not be able to do further investigation until a solid STR with high reproduce rate is provided.

Comment 10

[Chaochao Huang]

(In reply to Arthur Chen [:arthurcc] from comment #9)
> Normally loading alameda.js won't fail. There might be racing in gecko but
> there is not much information in the log. We may not be able to do further
> investigation until a solid STR with high reproduce rate is provided.

STR with high reproduce rate as below:

1、Click the Settings app icon in homescreen, and click 'Home' button immediately before the Settings app loading successfully.
2、Open other app such as video， music to make CPU busy for 1 minute.
3、Back to the Settings app

OBSERVED:
4. Failed to use options of Settings.

EXPECTED:
5. Use options of Settings normally.

The Flame also has this issue.


Arthur,

Help check this issue.

Thanks.

Comment 11

[Chaochao Huang]

Hi Arthur,

waitSeconds is 7s in alameda.js. As STR in Comment 10, because the cpu is busy during the 7s, alameda.js loading unsuccessfully leads to this issue. We can increase waitSeconds or make waitSeconds 0.

What do you think？

Comment 12

[Arthur Chen [:arthurcc][inactive after 6/30]]

As you suggested that waitSeconds is the key to this issue. I can reproduce this on master by simply opening settings app and put it into background immediately. The error came up after a few seconds without doing anything.

The waitSeconds helps for development by prompting an error when there are incorrect path, I will modify the build script to make it override wairSeconds to 0 but keep the default value when DEBUG=1.

Comment 13

[GitHub Autolander Bot]

Attachment: [gaia] crh0716:1150798 > mozilla-b2g:master

Comment 14

[Arthur Chen [:arthurcc][inactive after 6/30]]

Comment on attachment 8592633 [details] [review]
[gaia] crh0716:1150798 > mozilla-b2g:master

EJ, the solution was based on James' comment in the PR[1], which disable the timeout in the production build. Could you help review the patch? Thanks.

[1]: https://github.com/mozilla-b2g/gaia/pull/17587

Comment 15

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

Comment on attachment 8592633 [details] [review]
[gaia] crh0716:1150798 > mozilla-b2g:master

Thanks Arthur ! r+

Comment 16

[Arthur Chen [:arthurcc][inactive after 6/30]]

Thanks, EJ.

Comment 17

[GitHub Autolander Bot]

http://docs.taskcluster.net/tools/task-graph-inspector/#KImB1jY2R4Swl--IwaPCyA

The pull request failed to pass integration tests. It could not be landed, please try again.

Comment 18

[GitHub Autolander Bot]

Pull request has landed in master: https://github.com/mozilla-b2g/gaia/commit/57fade7eed933aac78af0d840cac6206f0019b34

Comment 19

[Vance Chen [:vchen][skype:vance.lucida][[e-mail]]]

Hi Vincent, Steven, could you help to land this one on 2.1s as well?

Thanks

Hi ChaoChao, just to let you know that this one has been fixed(but not yet land on 2.1s)

Thanks

Comment 20

[Vincent Liu[:vliu]]

v2.1s : https://github.com/mozilla-b2g/gaia/commit/b4aa95747416af5ffa147d5aea79a352ab236de4

Comment 21

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

This issue is verified fixed on the latest Nightly Flame 3.0 build.  Setting the verifyme tag so this will be checked on 2.1S (I do not have access to a device that can run it).

Actual Results: The settings app does not become unresponsive when it is minimized during startup.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150423010203
Gaia: 9d4f756aa35cb7f030a92f3c1f65fb55254ddd1d
Gecko: 0b202671c9e2
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0