If this is the same problem that I'm seeing, what's happening is that the
buffer and cache memory (as reported in top) is not being freed early
enough.
In my situation, what happens is that (over time), buffers+cache grows to
80MB or more (out of 320MB total available; no swap). Factoring in the
memory used by running processes, the uncommitted memory falls to <10MB.
Then, when Mozilla or StarOffice tries to allocate some more memory, the
OOM killer picks one of them instead of shrinking the cache.
I'd check the amount of memory allocated to buffers and cache after one
your OOM events and see if that explains why you're now seeing low memory
conditions with the same workload.
-
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/