Closed Bug 818510 Opened 13 years ago Closed 13 years ago

Homescreen sometimes hangs and/or crashes (possibly in OOM situations)

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:+)

RESOLVED WORKSFORME
B2G C3 (12dec-1jan)
blocking-basecamp +

People

(Reporter: st3fan, Assigned: vingtetun)

References

Details

(4 keywords)

Attachments

(1 file)

I hit the home button to go back to the home screen. It showed an empty home screen with just the background but no icons. After a few seconds it showed me the 'Homescreen is having problems' error. Hitting the 'Try again' button does not do anything. Logcat output attached to the bug.
Also, neither Close or Try Again do anything. Close should probably force-kill-restart the homescreen?
STR: 1. place a lot of images in the gallery (50+) 2. using the gallery app's shortcut to camera, take a picture 3. go back to the gallery app using the camera app's shortcut 4. edit image and save the image Expected: no hang/image saves Actual: hang, homescreen will crash (due to OOM?) I ran into this yesterday and the day before. You can't get the homescreen back by hitting home; you need to reboot the phone
blocking-basecamp: ? → +
Priority: -- → P2
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
Mass Modify: All un-milestoned, unresolved blocking-basecamp+ bugs are being moved into the C3 milestone. Note that the target milestone does not mean that these bugs can't be resolved prior to 12/10, rather C2 bugs should be prioritized ahead of C3 bugs.
Target Milestone: --- → B2G C3 (12dec-1jan)
Sending over to Vivien. This bug may morph into "Homescreen should better handle app OOM", if that's the root cause.
Assignee: nobody → 21
Keywords: hang, perf
Blocks: 796172
Summary: Homescreen is having problems (logcat attached) → Homescreen sometimes hangs and/or crashes (possibly in OOM situations)
Cjones, do you know why we're not restarting the Home Screen after the crash?
Flags: needinfo?(jones.chris.g)
Priority: P2 → P1
This sounds a lot like bug 820702, but the bug report was filed right around a known-good revision and the symptoms are slightly different. The only way the report in comment 0 could occur is if the b2g process and foreground apps are using enough memory that the homescreen can't restart. If we can reproduce that, it would definitely be a blocker because that would not meet the memory-usage acceptance requirements. Since this was filed though, we finally merged two really large memory wins to b2g18. So that may not repro anymore either. Comment 2 may be describing bug 820702. needinfo? -> nhirata to see if that still reproduces.
Flags: needinfo?(jones.chris.g) → needinfo?(nhirata.bugzilla)
I wonder if this bug can have been an occurrence of E.me living in the homescreen process. The fact that Stefan has seen this Try Again button seems like a content error to me not something that should have happened with a regular application. Otherwise I'm not able to reproduce the bug right now. The homescreen crash when OOM but he is restarted as expected.
Keywords: qawanted
I am not sure either. I cannot reproduce the issue with the STRs that I had before. I have seen issues revolving around the browser app and the content not loading but that is separate from this bug I believe. Should we mark this WFM until someone else reproduces?
Flags: needinfo?(nhirata.bugzilla)
Yep.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: