I'm not sure. Is there a way to check on a running phone via a shell? Otherwise, I guess I can sprinkle some printk's in the lowmemorykiller.c.
Thanks On Oct 12, 1:27 pm, Dianne Hackborn <hack...@android.com> wrote: > The limits are set with init.irc. Note that the default limits for level 14 > and 15 are quite hight, so if the problem is just the limits it means the > working set for your build of Android is significantly larger than that of > the stock system. Have you made sure that you have the android out of > memory killer built in your kernel? > > > > On Thu, Oct 8, 2009 at 3:16 PM, Anthony <m.bn...@gmail.com> wrote: > > > The device I'm working on isn't killing processes early enough, and I > > was wondering where I can change this limit. It seems like mm/ > > page_alloc.c and mm/oom_kill.c are related, but I don't understand the > > "zone"s involved. > > > My device starts having a ton of page faults and visually lagging, but > > there are numerous processes with oom_adj 14 and 15, so I was hoping > > there was an easily adjustable value I could play with to see what > > gives a better experience. > > > Thanks > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
