1043610 - [B2G][Homescreen]Blank screen is displayed when moving app icons if there are too many pages on homescreen

Status: RESOLVED DUPLICATE of bug 1042772

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

Description

[Ross Kuhlman ([e-mail])]

Attachment: HomescreenIconMovement.txt

If the user creates too many separate pages on the homescreen, a blank screen will be displayed after the user moves an icon on the homescreen. This happens most reliably if the app is moved to one of the pages at the bottom of the homescreen.

The screen will display appropriately again if the user scrolls up/down the homescreen. This issue occurs after 8 pages have been created on the homescreen.

Repro Steps:
1) Update a Flame to BuildID: 20140724040205
2) Long press an app icon on the homescreen to summon 'Edit' menu
3) Drag an app icon all the way to the bottom of the homescreen to create a new page
4) Repeat step 3 until there are at least 8 pages on the homescreen
5) Drag an app icon to the bottom page

Actual:
All icons disappear, user is shown a blank grey screen

Expected:
All homescreen details continue to display appropriately

Master M/C Environmental Variables:
Device: Flame Master M/C MOZ
BuildID: 20140724040205
Gaia: c72257b2d27135bfcd68e89dd584182797784016
Gecko: 06ac51c2b8a8
Version: 34.0a1
Firmware Version: v122


Keywords:

Repro frequency: 100%
Link to video of issue: https://www.youtube.com/watch?edit=vd&v=zDy94sLe6z4
See attached: logcat

Comment 1

[Ross Kuhlman ([e-mail])]

Issue does not occur in v2.0.

Issue DOES occur in Master M/C, regardless of memory setting

Comment 2

[Peter Bylenga [:PBylenga]]

Regression, but not going to nominate to block release as it is low visibility and can be recovered by a scroll.

Comment 3

[Jason Smith [:jsmith]]

Peter - I think you meant to put QAnalyst-Triage+ here. Can you fix this?

Comment 4

[Josh Schmitt [Joshs]]

I am able to repro this bug by long pressing an app on the last default page.

1. Scroll to the last default page after OTA/Flash
2. Long press on an app and hold for a few seconds

Due to this being a more common occurrence than previously thought, adding smoketest keyword.

Environmental Variables:
Device: Flame Master
Build ID: 20140728040209
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: a4dcfbebcb58
Version: 34.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Comment 5

[Peter Bylenga [:PBylenga]]

[Blocking Requested - why for this release]:
Smoketest blocker, more severe than previously determined.

Nominating to block with this new information, user does not need to add multiple pages, attempting to move the last icon on the last default page reproduces issue.

Requesting window.

Comment 6

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

This issue seems to have been caused by the fix for bug 1041510.  This bug caused about 3 days worth of builds where the device would restart whenever the bug was reproduced.  
I have included two logs with this window.  The first is the last confirmed working build to the first broken, 3 days and about 50 builds in between causes this pushlog to be huge.  
The second is just the last restart build to the first broken.  The only changelist in that log is bug 104150.

Mozilla-inbound Regression Window

Last Working 
Environmental Variables:
Device: Flame Master
BuildID: 20140719062420
Gaia: d839242c2a4a6a445cbd8bc2443acbdf712a19fc
Gecko: 9350909a3401
Version: 33.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Last restarting
Environmental Variables:
Device: Flame Master
BuildID: 20140722125758
Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3
Gecko: 7ce6d4ccc804
Version: 34.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


First Broken 
Environmental Variables:
Device: Flame Master
BuildID: 20140722133759
Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3
Gecko: b102fe6b3565
Version: 34.0a1 (Master) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Last working gaia / First broken gecko - Issue DOES occur
Gaia: d839242c2a4a6a445cbd8bc2443acbdf712a19fc
Gecko: b102fe6b3565

First broken gaia / Last working gecko - Issue does NOT occur
Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3
Gecko: 9350909a3401


Gecko Pushlog:  https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=9350909a3401&tochange=b102fe6b3565



Last restart gaia / First broken gecko - Issue DOEs occur
Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3
Gecko: b102fe6b3565

First broken gaia / Last restart gecko - Device restarts when reproducing
Gaia: cd50cb6ddeb430ddaf43e4fcf5774b9d262a8cf3
Gecko: 7ce6d4ccc804


Gecko Pushlog:  https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7ce6d4ccc804&tochange=b102fe6b3565

Comment 7

[Joshua Mitchell (Inactive)]

Broken by bug 1041510 ?

Comment 8

[Mathieu Agopian [:magopian]]

Did you needinfo? me on purpose? I don't know what information you're waiting from me?

Comment 9

[Timothy Nikkel (:tnikkel)]

Before bug 1041510 the situation here was just broken. So more likely the true cause is bug 1022612. And this bug sounds a lot like a dupe of bug 1042772.

Comment 10

[Kartikaya Gupta (email:[e-mail])]

What timothy said. Leaving open for now but feel free to dupe to 1042772.