Closed
Bug 1078786
Opened 10 years ago
Closed 10 years ago
[Settings] After browsing web, Settings may become unusable where no selection can be made
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:2.1+, b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WORKSFORME
blocking-b2g | 2.1+ |
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | affected |
People
(Reporter: onelson, Assigned: eragonj)
References
()
Details
(Keywords: regression, Whiteboard: [2.1-Daily-Testing])
Attachments
(2 files)
Description:
When the user enters into Settings after browsing the web for an undeterminate amount of time ( 2~8 minutes ), they will observe that they will be unable to perform any selection on any options menu for the duration that the 'Settings' app is open. Re-opening the app will reset the condition and restore functionality to 'Settings'.
Repro Steps:
1) Update a Flame device to BuildID: 20141006000205
2) Open 'Browser' app.
3) Search for 'youtube'.
4) Open YouTube mobile site.
5) Search for anything. *spend any amount of time, no videos were actually watched
6) Home to homescreen.
7) Open 'Settings' app.
8) Attempt to make a selection; observe UI.
Actual:
Selections cannot be made in Settings. Operator Services appears as a tab on the bottom of the page.
Expected:
Settings is navigable after web searching.
Environmental Variables:
Device: Flame 2.1
BuildID: 20141006000205
Gaia: 778ebac47554e1c4b7e9a952d73e850f58123914
Gecko: c4a4b04c617c
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
****************************************************************
DOES NOT OCCUR on 2.2 KK Master:
Results: Settings is navigable after web searching.
Enviromental Variables:
----------------------------------------
Device: Flame 2.2 Master
BuildID: 20141006040204
Gaia: 470826d13ae130a5c3d572d1029e595105485fb0
Gecko: e0d714f43edc
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
====================================================================
Repro frequency: 2/3
See attached:
video- http://youtu.be/GEugP7ebO9k
logcat
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [2.1-Daily-Testing]
Reporter | ||
Comment 1•10 years ago
|
||
Reproed in 2.2 Master after another attempt; attaching logcat.
Results: Settings becomes unusable after browsing web, may scroll but make no selections.
Enviromental Variables:
----------------------------------------
Device: Flame 2.2 Master
BuildID: 20141006040204
Gaia: 470826d13ae130a5c3d572d1029e595105485fb0
Gecko: e0d714f43edc
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Reporter | ||
Updated•10 years ago
|
Comment 2•10 years ago
|
||
QAWanted for branch checks after specific steps found.
Flags: needinfo?(pbylenga)
Keywords: qawanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Comment 3•10 years ago
|
||
Unable to repro on Flame 2.2 or Flame 2.1 engineering build with shallow flash. Also unable to repro on the nightly 2.1 build that the reporter posted using full flash.
Actual result: After spending some time wandering the browser, the Settings will respond to taps after it is launched.
Flame 2.2
BuildID: 20141007130518
Gaia: 9050edcda308b65d86577c8ed0eedc5c568d8e44
Gecko: 0c8ae792f1c0
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flame 2.1
BuildID: 20141007075118
Gaia: da328c6cbabf2cffc2d362e282cacc93325d1f43
Gecko: aebe54593d60
Platform Version: 34.0a2
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Leaving qawanted tag for others to attempt.
Comment 4•10 years ago
|
||
Tested with Shallow Flash on 319mb using Engineering builds.
This bug does NOT repro on Flame kk build: flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK
Actual Result: Settings page has functionality each time I return from Youtube.com after spending 10 or so minutes on that site.
Repro Rate: 0/15
Environmental Variables:
Device: Flame Master KK
BuildID: 20141007183418
Gaia: 0bc74ce502672cf0265b24cf3a25d117c3de5e71
Gecko: e4cfacb76830
Version: 35.0a1 (Master)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141008055818
Gaia: 7ef2e1e59637a34ca4489c329b3bdee93df3ac6c
Gecko: e3d495eb85c6
Version: 34.0a2
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141008010820
Gaia: 14b50318e1f3cdd571566316acb49a4451d7a0af
Gecko: 38272cbff5de
Version: 32.0 (2.0)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Leaving QAWanted tag.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Comment 5•10 years ago
|
||
Oliver - my team is having some trouble getting a repro - can you see if you can still reproduce this bug?
Comment 6•10 years ago
|
||
Ok a few of us have been able to finally reproduce this bug on 2.1 KK
We believe that it's a memory issue with a ton of apps open all at once. Then you go to Settings app and you are unable to tap on any of the options.
This seems like it is a memory issue where certain branches are not limiting the number of apps that can be open at one time. Many issues are tied to this problem and this looks like one of them.
Tested with Shallow Flash on 319mb using Engineering builds
This bug repro's on Flame KK builds: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK
Actual Results: Settings becomes unresponsive when tapping on options in the settings app after having 10+ apps open on the Flame.
Repro Rate: 5/6
Environmental Variables:
Device: Flame Master KK
BuildID: 20141007183418
Gaia: 0bc74ce502672cf0265b24cf3a25d117c3de5e71
Gecko: e4cfacb76830
Version: 35.0a1 (Master)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141008055818
Gaia: 7ef2e1e59637a34ca4489c329b3bdee93df3ac6c
Gecko: e3d495eb85c6
Version: 34.0a2
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
-----------------------------------------------------------------
This bug does NOT repro on Flame kk build: Flame 2.0 KK
Actual Result: Unable to get any issues where a user can't tap on options in the settings menu.
Repro Rate: 0/5
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141008010820
Gaia: 14b50318e1f3cdd571566316acb49a4451d7a0af
Gecko: 38272cbff5de
Version: 32.0 (2.0)
Firmware Version: L1TC10011800
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → unaffected
Flags: needinfo?(jmitchell)
Keywords: regression
QA Contact: croesch
Comment 7•10 years ago
|
||
I incorrectly listed it happens in Flame 2.0 KK. It does NOT happen in 2.0 KK because 2.0 seems to limit the apps correctly not allowing memory issues.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(onelson)
Flags: needinfo?(jmitchell)
See Also: → 1080239
Comment 8•10 years ago
|
||
[Blocking Requested - why for this release]:
This is a regression and many end users will not close out their opened apps so this will lead the user to non functional buttons.
Let's get a regression window here since this appears to have a 90% repro rate.
Comment 9•10 years ago
|
||
Non-functional settings is a bad regression so 2.1+.
blocking-b2g: 2.1? → 2.1+
Updated•10 years ago
|
Assignee: nobody → arthur.chen
Updated•10 years ago
|
QA Contact: croesch
Comment 10•10 years ago
|
||
4 testers have tried to reproduce this issue today and we have been unable to get any reproductions. We have checked on recent builds and the past builds where we would be looking for windows in.
Flags: needinfo?(jmitchell)
Comment 11•10 years ago
|
||
It seems like the repro rate on this issue is highly variable. I'm leaving this tagged and in our Queue for now but a regression range might not be able to be gotten with such an inconsistent repro.
Flags: needinfo?(jmitchell)
Comment 12•10 years ago
|
||
It seems the bug is not reproducible. Un-assign from myself.
Assignee: arthur.chen → nobody
Comment 13•10 years ago
|
||
Also unable to reproduce - let's close this as WFM - please reopen if this occurs again (hopefully with a solid repro)
Device: Flame 2.2
Build ID: 20141021132208
Gaia: 82174cee5ede9f23aedad8a39f8b8cdc1ae710c4
Gecko: 15099ba111e8
Version: 36.0a1 (2.2)
Firmware Version: L1TC00011880 (v188)
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
Status: NEW → RESOLVED
Closed: 10 years ago
Keywords: regressionwindow-wanted
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 14•10 years ago
|
||
I was able to reproduce this issue 100% by following the steps listed below.
Steps to Reproduce:
1. Do the XHeavy script.
2. Open the browser app and type in a few letters in the search bar to generate several results, and then close the app.
3. Open messages app and scroll quickly towards the bottom of the list, but not all the way.
4. Press the home button to minimize the app.
5. Open contacts app, minimize the app, then open dialer app and minimize the app.
6. Open the browser app back up, tap on the search bar and quickly select one of the results.
7. Then minimize the app, and open the gallery app and scroll through some of the pictures quickly.
8. Press the home button to minimize the gallery app, and then open the settings app.
9. While the settings app loads, press and hold the home button to bring up the task manager.
10. Slide through the apps to the left until the user reaches the end.
11. Press the home button to close the task manager, and select the settings app again.
12. Notice the settings menu will become unresponsive.
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Comment 15•10 years ago
|
||
We keep seeing this issue in our daily testing but the steps are still not 100% to do a regression window. Adding steps-wanted instead.
Keywords: regressionwindow-wanted → steps-wanted
Comment 16•10 years ago
|
||
Arthur, could you try to see comment 14 is reliable enough to reproduce this issue?
Flags: needinfo?(arthur.chen)
Comment 17•10 years ago
|
||
I used Flame master with x-heavy load and the messaging app did not launch correctly. It did not display any of the messages. Following the STR and before I launching settings app b2g went crashed. The issue seems to be cross the device. I'll keep trying other builds and loads.
Flags: needinfo?(arthur.chen)
Assignee | ||
Comment 18•10 years ago
|
||
Not sure whether I can reproduce this or not, let me take this first.
Assignee: nobody → ejchen
Assignee | ||
Comment 19•10 years ago
|
||
Weird, I tried to make `reference-workload-x` (x is from light to x-heavy) but my phone all became a brick after flashing. Not sure what's going on, I would try to find sometime to try again.
Assignee | ||
Comment 20•10 years ago
|
||
Finally, I successfully ran `make reference-workload-x-heavy` and pushed data into flame, but my flame seems a little bit out of control.
By following steps in comment 14, I got different results than the others.
> 1. Do the XHeavy script.
> 2. Open the browser app and type in a few letters in the search bar to
> generate several results, and then close the app.
> 3. Open messages app and scroll quickly towards the bottom of the list, but
> not all the way.
Message app shows a white screen and I can't do anything on it.
> 4. Press the home button to minimize the app.
> 5. Open contacts app, minimize the app, then open dialer app and minimize
> the app.
Contacts app shows a white screen and I can't do anything on it.
> 6. Open the browser app back up, tap on the search bar and quickly select
> one of the results.
> 7. Then minimize the app, and open the gallery app and scroll through some
> of the pictures quickly.
> 8. Press the home button to minimize the gallery app, and then open the
> settings app.
Gallery works well and it keeps loading images from database.
> 9. While the settings app loads, press and hold the home button to bring up
> the task manager.
> 10. Slide through the apps to the left until the user reaches the end.
> 11. Press the home button to close the task manager, and select the settings
> app again.
> 12. Notice the settings menu will become unresponsive.
When doing tests, Settings always can work well and the menu is still responsive and you can even click it.
But after doing xHeavy script, my phone would keep rebooting by itself randomly and I don't know why.
Based on what I got here, not sure what to do next !? And if this is really a memory issue, is there any plan for us to do next ?
== device info ==
Gaia-Rev 7918024c737c4570cacd784f267e28737ae05dea
Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/2114ef80f6ae
Build-ID 20141105160209
Version 36.0a1
Device-Name flame
FW-Release 4.4.2
FW-Incremental 27
FW-Date Thu Sep 4 14:59:02 CST 2014
Bootloader L1TC10011800
Comment 21•10 years ago
|
||
qawanted to see if can reproduce the same issue as Comment 20, if so, we need to file per app bug
Keywords: qawanted
Comment 22•10 years ago
|
||
Comment 20 sounds like a platform bug we should be looking at b2g-info/logcat and see if the content process and frames etc are still working. Filing per-app bug is not likely to help (other than taking this bug off from Settings comp).
Comment 23•10 years ago
|
||
Any update for this bug?
Assignee | ||
Comment 24•10 years ago
|
||
(In reply to Ken Chang[:ken] from comment #23)
> Any update for this bug?
We already set qawanted, regressions, steps-wanted but there is no response yet.
==
Based on comment 20, comment 21 and comment 22, Oliver (reporter) can you check again about this bug ? And if this is really a platform bug (We suspect it is), can you help to change the component ? Thanks.
Flags: needinfo?(onelson)
Comment 25•10 years ago
|
||
I followed the steps in comment 14 and never could get this bug to occur. I spoke with the reporter on this and it sounds like operator services may need to listed at the bottom of the settings page for this bug to occur? After flashing/Resetting, quickly going through FTU then to settings, I'm able to get operator services to briefly appear at the bottom of the settings page but then it quickly goes away. So if this Operator services hanging around in settings is needed to reproduce this bug then this might give us a lead on what could be causing this bug.
Any ideas on that?
Tested with Shallow Flash on 319mb using Engineering builds
Repro Rate: 0/12
Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141117031129
Gaia: 10b84fae70cfab428030cc086b433f89ac440c14
Gecko: bc3751255fd1
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Comment 26•10 years ago
|
||
(In reply to howie [:howie] from comment #21)
> qawanted to see if can reproduce the same issue as Comment 20, if so, we
> need to file per app bug
Now that I've provided information on the steps for comment 14, let me address comment 20.
The white screen issue you are most likely running into is a known issue about settings occasionally just loading as a white screen. Going into card view and then tapping on the settings card should fix this.
As far as the rebooting constantly when doing X-heavy script, I just ran the script on my Flame with 2.1 set to 319mem. I saw no issues with here. Every app i went into loaded all the correct information. So i can't explain your experience.
Hope this provides some help.
Assignee | ||
Comment 27•10 years ago
|
||
(In reply to Cody Roesch [:croesch] from comment #26)
> The white screen issue you are most likely running into is a known issue
> about settings occasionally just loading as a white screen. Going into card
> view and then tapping on the settings card should fix this.
>
No, at that time, I saw white screen in Contacts & Message app (I can see top frames with action buttons by the way) not in Settings app.
> As far as the rebooting constantly when doing X-heavy script, I just ran the
> script on my Flame with 2.1 set to 319mem. I saw no issues with here. Every
> app i went into loaded all the correct information. So i can't explain your
> experience.
>
> Hope this provides some help.
Demo : https://www.youtube.com/watch?v=DgBt1RLQeBU
I recorded a demo showing what I saw in Contact & Message apps (white content with clickable items). In this demo, I did follow the STR but forgot to open gallery app but this won't affect anything. (I did try with a full STR but forgot to record, so I uploaded this one)
Based on this demo, you can notice that at first when I open contact & message apps, they are all white without any contents and I can't do too much on it, but after a while, when I come back to these apps, the data would be shown on the screen. (kinda weird)
For settings app, you can see that no matter when we get into settings app, it would always work perfect without any problem.
And about the missing operator menu items, I did try several times and noticed that if you flash with a clean build from PVT, they will always be shown there. But after flashing x-heavy, they are gone. From users' perspective (users won't flash x-heavy) and the description of this bug (settings may become unusable), this is a false alarm and can be ignored. So, for missing operator menu items in x-heavy, please file another bug and cc us + stk fellows.
Comment 28•10 years ago
|
||
We should close the bug if the original reported issue cannot be reproduced anymore. Issues mentioned in comment 26 seem like a separate issue and we can file a separate bug tracking it.
Comment 29•10 years ago
|
||
based on Comment 25, resolved works for me.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
Updated•10 years ago
|
Keywords: qawanted,
steps-wanted
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(onelson)
You need to log in
before you can comment on or make changes to this bug.
Description
•