Messages in this thread | | | Date | Fri, 24 Feb 2012 23:52:38 +0200 | Subject | Re: [PATCH] oom: add sysctl to enable slab memory dump | From | Pekka Enberg <> |
| |
On Fri, 24 Feb 2012, Josef Bacik wrote: >> Um well yeah, I'm rewriting a chunk of btrfs which was rapantly leaking memory >> so the OOM just couldn't keep up with how much I was sucking down. This is >> strictly a developer is doing something stupid and needs help pointing out what >> it is sort of moment, not a day to day OOM.
On Fri, Feb 24, 2012 at 11:45 PM, David Rientjes <rientjes@google.com> wrote: > If you're debugging new kernel code and you realize that excessive amount > of memory is being consumed so that nothing can even fork, you may want to > try cat /proc/slabinfo before you get into that condition the next time > around, although I already suspect that you know the cache you're leaking. > It doesn't mean we need to add hundreds of lines of code to the kernel. > Try kmemleak.
Kmemleak is a wonderful tool but it's also pretty heavy-weight which makes it inconvenient in many cases.
Pekka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |