current settings & before the first app crash: - the home screen has background image larger than the screen (automatically cropped). set with the gallery application. - no wifi / data connection. - locale fr. - "magic stones" app installed & launched multiple times without any cache of it. - changed multiple time the locale. ** Logcat obtained when starting the setting app: I/IdleService( 107): next timeout 1000 msec from now I/IdleService( 107): SetTimerExpiryIfBefore: next timeout 1000 msec from now I/IdleService( 107): reset timer expiry to 1010 msec from now I/IdleService( 107): Reset idle timeout: tell observer 47df4960 user is back E/GeckoConsole( 107): Content JS INFO at app://system.gaiamobile.org/js/window_manager.js:1086 in createFrame: %%%%% Launching Param�tres as remote (OOP) D/memalloc( 107): /dev/pmem: Allocated buffer base:0x4ab00000 size:614400 offset:1687552 fd:79 D/memalloc( 107): /dev/pmem: Allocated buffer base:0x4ab00000 size:614400 offset:2301952 fd:93 D/memalloc( 107): /dev/pmem: Allocated buffer base:0x4ab00000 size:614400 offset:3530752 fd:141 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ac9c000 size:614400 offset:1687552 fd:79 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ad32000 size:614400 offset:2301952 fd:93 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4adc8000 size:614400 offset:2916352 fd:120 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ab00000 size:245760 offset:0 fd:130 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4abfc000 size:8192 offset:1032192 fd:135 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ab3c000 size:122880 offset:245760 fd:138 D/memalloc( 3928): /dev/pmem: Unmapping buffer base:0x44600000 size:3530752 offset:2916352 D/memalloc( 3928): /dev/pmem: Unmapping buffer base:0x4233f000 size:245760 offset:0 D/memalloc( 3928): /dev/pmem: Unmapping buffer base:0x43f00000 size:1040384 offset:1032192 D/memalloc( 3928): /dev/pmem: Unmapping buffer base:0x42c00000 size:368640 offset:245760 D/memalloc( 107): /dev/pmem: Allocated buffer base:0x4ab00000 size:614400 offset:1687552 fd:79 I/IdleService( 107): Get idle time: time since reset 916 msec I/IdleService( 107): Idle timer callback: current idle time 916 msec I/IdleService( 107): next timeout 82 msec from now I/IdleService( 107): SetTimerExpiryIfBefore: next timeout 81 msec from now I/IdleService( 107): reset timer expiry to 90 msec from now I/IdleService( 107): Get idle time: time since reset 1020 msec I/IdleService( 107): Idle timer callback: current idle time 1020 msec I/IdleService( 107): next timeout 4294967293979 msec from now I/IdleService( 107): SetTimerExpiryIfBefore: next timeout 4294967293978 msec from now I/IdleService( 107): reset timer expiry to 4294967293988 msec from now I/IdleService( 107): Idle timer callback: tell observer 47df4960 user is idle I/IdleService( 107): Get idle time: time since reset 1022 msec D/memalloc( 107): /dev/pmem: Allocated buffer base:0x4ab00000 size:614400 offset:2301952 fd:93 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ac9c000 size:614400 offset:1687552 fd:79 D/memalloc( 107): /dev/pmem: Freeing buffer base:0x4ae5e000 size:614400 offset:3530752 fd:141 ** adb shell > b2g-ps APPLICATION USER PID PPID VSIZE RSS WCHAN PC NAME b2g root 107 1 235916 110300 ffffffff 400ee330 S /system/b2g/b2g Homescreen app_3928 3928 107 68172 19292 ffffffff 40042330 S /system/b2g/plugin-container Cost Control app_4817 4817 107 60924 10604 ffffffff 400a4330 S /system/b2g/plugin-container (Preallocated a app_5257 5257 107 55676 11420 ffffffff 4010a330 S /system/b2g/plugin-container Seen: - the last buggy start-up screenshot is shown, but nothing more appear. (see attachment) Device info: - OS: 1.0.0 - Hardware: nice - Platform: 18.0 - Build id: 20121226070202 - Channel: beta - Git info: 2012-12-26 15:10:59 (unknown sha1)

If you can reproduce this, can you try running |$ adb shell ps| in addition to |$ adb shell b2g-ps| ?

Does this happen with a more recent build?

(In reply to Chris Jones [:cjones] [:warhammer] from comment #1) > If you can reproduce this, can you try running |$ adb shell ps| in addition > to |$ adb shell b2g-ps| ? I did a top when I dumped all these, hopefully I still have them in my shell log: User 0%, System 2%, IOW 0%, IRQ 0% User 2 + Nice 0 + Sys 8 + Idle 298 + IOW 0 + IRQ 0 + SIRQ 0 = 308 PID PR CPU% S #THR VSS RSS PCY UID Name 5310 0 2% R 1 1056K 416K fg root top 117 0 0% S 2 2220K 196K fg root /system/bin/akmd8962_new 3928 0 0% S 11 68172K 17952K fg app_3928 /system/b2g/plugin-container 67 0 0% S 1 0K 0K fg root irq/82-0-000c 138 0 0% S 5 4532K 216K fg root /sbin/adbd 5182 0 0% S 1 0K 0K fg root kworker/0:0 9 0 0% S 1 0K 0K fg root sync_supers 10 0 0% S 1 0K 0K fg root bdi-default 11 0 0% S 1 0K 0K fg root kblockd 12 0 0% S 1 0K 0K fg root khubd 13 0 0% S 1 0K 0K fg root l2cap 14 0 0% S 1 0K 0K fg root a2mp 15 0 0% S 1 0K 0K fg root modem_notifier 16 0 0% S 1 0K 0K fg root smd_channel_clo 19 0 0% S 1 0K 0K fg root rpcrouter 20 0 0% S 1 0K 0K fg root rpcrotuer_smd_x 21 0 0% S 1 0K 0K fg root krpcserversd 23 0 0% D 1 0K 0K fg root voicememo_rpc 24 0 0% S 1 0K 0K fg root kadspd 25 0 0% D 1 0K 0K fg root krmt_storagecln 26 0 0% D 1 0K 0K fg root krmt_storagecln 27 0 0% S 1 0K 0K fg root rmt_storage 28 0 0% S 1 0K 0K fg root kswapd0 29 0 0% S 1 0K 0K fg root fsnotify_mark 30 0 0% S 1 0K 0K fg root crypto 43 0 0% S 1 0K 0K fg root mdp_dma_wq 44 0 0% S 1 0K 0K fg root mdp_vsync_wq 45 0 0% S 1 0K 0K fg root mdp_hist_wq 46 0 0% S 1 0K 0K fg root mdp_pipe_ctrl_w 48 0 0% S 1 0K 0K fg root kgsl-3d0 55 0 0% S 1 0K 0K fg root k_rmnet_mux_wor 56 0 0% S 1 0K 0K fg root f_mtp 57 0 0% S 1 0K 0K fg root file-storage 59 0 0% S 1 0K 0K fg root diag_wq 60 0 0% S 1 0K 0K fg root diag_cntl_wq 61 0 0% S 1 0K 0K fg root atmel_wq 62 0 0% D 1 0K 0K fg root krtcclntd 63 0 0% D 1 0K 0K fg root krtcclntcbd 64 0 0% S 1 0K 0K fg root kfmradio 65 0 0% D 1 0K 0K fg root kbatteryclntd 66 0 0% D 1 0K 0K fg root kbatteryclntcbd 68 0 0% S 1 0K 0K fg root KXTIK Workqueue 69 0 0% S 1 0K 0K fg root irq/92-kxtik-ir 70 0 0% S 1 0K 0K fg root iewq 71 0 0% D 1 0K 0K fg root kinteractiveup 72 0 0% S 1 0K 0K fg root mmcsdcc_host3 73 0 0% S 1 0K 0K fg root irq/80-msm-sdcc 74 0 0% S 1 0K 0K fg root mmcsdcc_host1 75 0 0% S 1 0K 0K fg root mmcsdcc_host2 1 0 0% S 1 480K 336K fg root /init 77 0 0% S 1 0K 0K fg root krfcommd 79 0 0% D 1 0K 0K fg root khsclntd 80 0 0% S 1 312K 168K fg root /sbin/ueventd 81 0 0% S 1 0K 0K fg root mmcqd/0 82 0 0% S 1 0K 0K fg root jbd2/mmcblk0p19 83 0 0% S 1 0K 0K fg root ext4-dio-unwrit 87 0 0% S 1 0K 0K fg root mmcqd/1 88 0 0% S 1 0K 0K fg root jbd2/mmcblk0p22 89 0 0% S 1 0K 0K fg root ext4-dio-unwrit 93 0 0% S 1 0K 0K fg root jbd2/mmcblk0p10 94 0 0% S 1 0K 0K fg root ext4-dio-unwrit 98 0 0% S 1 0K 0K fg root jbd2/mmcblk0p21 99 0 0% S 1 0K 0K fg root ext4-dio-unwrit 101 0 0% S 1 892K 100K fg system /system/bin/servicemanager 102 0 0% S 3 4080K 364K fg root /system/bin/vold 106 0 0% S 2 3372K 164K fg root /system/bin/fakeperm 107 0 0% S 38 221196K 93896K fg root /system/b2g/b2g 108 0 0% S 1 880K 120K fg radio /system/bin/rilproxy 109 0 0% S 6 7568K 380K fg root /system/bin/netd 110 0 0% S 1 760K 88K fg root /system/bin/debuggerd 111 0 0% S 14 21280K 2144K fg radio /system/bin/rild 112 0 0% S 2 12104K 864K fg drm /system/bin/drmserver 113 0 0% S 6 20084K 1168K fg media /system/bin/mediaserver 114 0 0% S 1 1388K 140K fg bluetoot /system/bin/dbus-daemon 115 0 0% S 1 896K 108K fg root /system/bin/installd 116 0 0% S 1 1792K 176K fg keystore /system/bin/keystore 128 0 0% S 3 6004K 124K fg root /system/bin/rmt_storage 133 0 0% S 1 0K 0K fg root k_gserial 135 0 0% S 1 0K 0K fg root k_gsmd 153 0 0% S 1 832K 124K fg shell /system/bin/sh 192 0 0% S 5 5532K 312K fg radio /system/bin/qmuxd 194 0 0% S 5 5692K 376K fg radio /system/bin/netmgrd 339 0 0% D 1 0K 0K fg root audmgr_rpc 604 0 0% S 1 0K 0K fg root cfg80211 607 0 0% S 1 0K 0K fg root ath6kl 1527 0 0% D 1 0K 0K fg root kworker/u:0 4733 0 0% Z 1 0K 0K fg app_4733 Gecko_IOThread 4817 0 0% S 11 60924K 10756K fg app_4817 /system/b2g/plugin-container 4995 0 0% S 1 0K 0K fg root ksdioirqd/mmc2 5140 0 0% S 1 0K 0K fg root kworker/u:1 5141 0 0% S 1 0K 0K fg root kworker/0:1 5181 0 0% S 1 0K 0K fg root flush-179:0 5196 0 0% Z 1 0K 0K fg app_5196 Gecko_IOThread 5228 0 0% S 11 61960K 17916K fg app_5228 /system/b2g/plugin-container 5246 0 0% S 1 0K 0K fg root kworker/u:2 5257 0 0% S 10 55676K 11788K fg app_5257 /system/b2g/plugin-container 5299 0 0% S 1 836K 428K fg root binder 2 0 0% S 1 0K 0K fg root kthreadd 3 0 0% S 1 0K 0K fg root ksoftirqd/0 6 0 0% S 1 0K 0K fg root khelper 7 0 0% S 1 0K 0K fg root suspend_sys_syn 8 0 0% S 1 0K 0K fg root suspend (In reply to Andrew Overholt [:overholt] from comment #2) > Does this happen with a more recent build? I don't know why you ask me, I am stuck with the testdriver versions. The last one being the one release that I have use to report this Bug. As I cannot reproduce it I don't know if I would even be able to provide a STR. I did notice a potential OOM, but this is quite difficult to determine because GCs are not happening all the time. Based on how this potential OOM was leaking I don't think it might be related to this bug. potential OOM STR: (settings: language fr) - Open magic stones (without any connectivity, and any cache of it) - Close the message mentioning a re-try. - run under an already connected adb shell the command b2g-ps, and see the memory growing by 200k each time. When a GC happen it will reduce the memory back to a minimal level which was higher than the after the last GC. - Repeat this a lot of times (sorry) This procedure was leaky at the time where the settings app was not starting anymore. Unfortunately, I was not able to reproduce after restarting the phone.

(In reply to Nicolas B. Pierron [:pierron] [:nbp] from comment #3) > (In reply to Chris Jones [:cjones] [:warhammer] from comment #1) > 4733 0 0% Z 1 0K 0K fg app_4733 Gecko_IOThread > 4817 0 0% S 11 60924K 10756K fg app_4817 > /system/b2g/plugin-container > 5196 0 0% Z 1 0K 0K fg app_5196 Gecko_IOThread > 5228 0 0% S 11 61960K 17916K fg app_5228 > /system/b2g/plugin-container These usually represent failed fork+execs. Handling that is bug 823474, which we may want to fix based on the evidence here. However, your "real bug" is the excessive memory usage. Nicolas, can you run $ cd $b2g $ python tools/get_about_memory.py and attach the generated file here? That will help us understand where the memory is going.

(In reply to Chris Jones [:cjones] [:warhammer] from comment #4) > Nicolas, can you run > > $ cd $b2g > $ python tools/get_about_memory.py > > and attach the generated file here? That will help us understand where the > memory is going. I cannot reproduce this bug, but I will keep this in mind if I see a similar issue in the future.

(In reply to Nicolas B. Pierron [:pierron] [:nbp] from comment #5) > I cannot reproduce this bug Okay, but if it comes back, please re-nom. Thanks!

clean the qawanted, please add if needed