Closed Bug 968628 Opened 10 years ago Closed 10 years ago

clicking e.me collection during homescreen launch can leave user in broken state

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 975917

People

(Reporter: bkelly, Unassigned)

Details

While testing bug 965369 I managed to get my 1.3 device into an unusable state.  Rough steps to reproduce:

1) Launch high memory app, for example poppit
2) Get homescreen killed in the background due to OOM
3) Hit home button to leave app and return to homescreen
4) While homescreen is launching and app is OOM'ing, click on one of the e.me collections
5) Notice you cannot exit collection search mode by clicking X or home button.  Searching does not work either.  Only solution is to reboot.

This was in the logcat:

E/GeckoConsole( 3030): [JavaScript Error: "TypeError: currentSettings is null" {file: "app://homescreen.gaiamobile.org/everything.me/modules/Collection/Collection.js" line: 116}]

I haven't been able to reproduce so far.
Keywords: steps-wanted
Ben, in case you are able to consistently reproduce, can you please try this patch and see if it fixes the issue?
https://github.com/EverythingMe/gaia/commit/b3aeda9c9fd4d2e6681e832f8e4c0b7c03886677

Thanks.
Amir, I'm not sure I will have time to look at this any time soon.  This seems like a pretty safe fix, though.  Maybe we could review and land it as a defensive measure?
Fixed in bug 975917.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Keywords: steps-wanted
You need to log in before you can comment on or make changes to this bug.