I notice lately while using the get_about_memory script with the emulator, gaia on the emulator reports that the homescreen has crashed (crash reporter) and the terminal notes "Warning: Child 138 exited during memory reporting". The emulator does seem to recover ok (homescreen reappears after the crash) and the memory dump is completed. Reproduced again today with a Mar-5 TBPL emulator build, logcat attached. Note from johns: "This sounds like a b2g bug that should be filed. It's expected that the phone kill old background tasks when it needs more ram, but I doubt we intend to nuke the home screen with an error dialog :-/" Note from gsvelto: "The homescreen can get killed by the LMK when we're low on memory but this won't trigger the crash screen. It sounds to me that we hit an actual bug here, maybe a defective memory reporter that segfaults the homescreen when computing memory usage. To figure out what's going on we could hook up gdb to the homescreen process, let it run, then run get_about_memory.py and see where things go boom."

Note: This is not exactly 'blocking' AWSY automation however I'm guessing that the homescreen crash and app restart could inadvertently effect the resulting memory use values.

Update: This still happens, tried it today with the latest TBPL emulator build.