997581 - loading call log in dialer for the first time kills the homescreen app or triggers memory pressure

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Dialer, defect, P2)

Description

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I'm using a self-built master build on a hamachi (256MB), most recently updated on Monday of this week (April 14).  I have profile data going back over a little more than a year, so I have a decent-sized call log, though nothing I can't scroll through in 30 seconds.

Steps to reproduce:
 1. hold down the home button to show the app switcher
 2. close the Phone app (dialer) if it's running
 3. click on the phone icon on the homescreen
 4. switch to the call log tab
 5. tap the home button to return to the homescreen

Actual results:  Homescreen takes a few seconds to show up because it's been killed, presumably due to low memory

Expected results:  Switching to the call log shouldn't use enough memory to kill the homescreen.

This started happening for me on master about 1-2 weeks ago.  I'm not sure if that's because there was a regression, or if the size of my call history just went past some threshold.

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Actually, doing this:
  while true; do adb shell b2g-info; sleep 0.2; done
shows we're not actually killing the homescreen.  Fabrice suggests maybe we're sending memory pressure notifications and discarding images, and then it takes time for the homescreen to come back from it.

Comment 2

[Gabriele Svelto [:gsvelto]]

Have you tried reproducing this issue using the gaia reference workloads? We might have introduce a significant memory regression if the call log alone is capable of pushing an Hamachi into a low memory condition.

Comment 3

[Johan Lorenzo [:jlorenzo] - On PTO - Back on July 28th]

This issue is not reproducible anymore on the Flame 319MB. The homescreen doesn't get OOMed while we are in the Dialer.