988239 - [MTBF][Memory Report] get_about_memory.py causing other apps to be closed due to memory usage

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: MTBF, defect)

Description

[Walter Chen[:ypwalter][:wachen]]

Per discussion with Kyle, I am opening this up. I don't think that it is actually a bug, but maybe reducing the memory using by get_about_memory can be helpful in many ways: 
1. won't affecting the test running
2. won't make window manager to close other apps too often
3. less affecting when devs/qas try to reproduce problems and take snapshot about memory simultaneously

Kyle, sorry for all these bothering and thank you in advance for helping on these bugs. Should you need any help, I am either in Moz space or QA block with Paul, Al, Askeing, William, ...and all other QAs.

Comment 1

[Walter Chen[:ypwalter][:wachen]]

PS. not actually a critical blocker for MTBF, but it will surely help a lot.

Comment 2

[Walter Chen[:ypwalter][:wachen]]

http://mtbf-1.corp.tpe1.mozilla.com:8080/job/mtbf.logcat.multi/label=mtbf-2/7/console
This might be related.

I/GonkMemoryPressure(  136): Checking to see if memory pressure is over.
I/GonkMemoryPressure(  136): Memory pressure is over.
I/GonkMemoryPressure(11400): Checking to see if memory pressure is over.
I/GonkMemoryPressure(11400): Memory pressure is over.
I/GonkMemoryPressure(11449): Checking to see if memory pressure is over.
I/GonkMemoryPressure(11449): Memory pressure is over.

Comment 3

[Walter Chen[:ypwalter][:wachen]]

LOGCAT
https://www.dropbox.com/s/l1s1opk55foab3b/mtbf-2_7th.logcat

Comment 4

[Eric Rahm [:erahm]]

Walter is this still an issue for you? I'd like to track down which reporter is causing OOMs if so. In more recent builds I'd expect to see something like the following in the logcat:

I/Gecko:DumpUtils( 4975): FifoWatcher(command:memory report) dispatching memory report runnable.
I/Gecko:DumpUtils( 4975): FifoWatcher closing and re-opening fifo.
E/GeckoConsole( 4975): nsIMemoryInfoDumper dumped reports to /data/local/tmp/memory-reports/unified-memory-report-1407976072-4975.json.gz
I/Gecko:DumpUtils( 4975): FifoWatcher(command:gc log) dispatching GC/CC log runnable.
I/Gecko:DumpUtils( 4975): FifoWatcher closing and re-opening fifo.
E/GeckoConsole( 4975): Garbage Collector log dumped to /data/local/tmp/memory-reports/gc-edges.4975.1407976076.log
E/GeckoConsole( 4975): Cycle Collector log dumped to /data/local/tmp/memory-reports/cc-edges.4975.1407976076.log
E/GeckoConsole( 4975): Garbage Collector log dumped to /data/local/tmp/memory-reports/gc-edges.6603.1407976076.log
E/GeckoConsole( 4975): Garbage Collector log dumped to /data/local/tmp/memory-reports/gc-edges.5176.1407976076.log
E/GeckoConsole( 4975): Cycle Collector log dumped to /data/local/tmp/memory-reports/cc-edges.6603.1407976076.log
E/GeckoConsole( 4975): Garbage Collector log dumped to /data/local/tmp/memory-reports/gc-edges.5175.1407976076.log
E/GeckoConsole( 4975): Garbage Collector log dumped to /data/local/tmp/memory-reports/gc-edges.6021.1407976076.log

If there's an LMK/OOM message around that I think we can narrow down what's happening.

Comment 5

[Walter Chen[:ypwalter][:wachen]]

We stopped using get_about_memory around 2014 April due to all kinds of difficulties encounted and not solved. I haven't run it for a long time.

Comment 6

[BMO Automation]

Firefox OS is not being worked on