Messages in this thread | | | Subject | 2.0.33 runs out of memory when using mremap ??? | Date | Tue, 31 Mar 1998 14:27:10 +0200 (Funky) | From | "Matthias Urlichs" <> |
| |
strace excerpt, while analyzing a big HTTP log file:
>write(4, "e] (WinNT; I ;Nav)\" http://www."..., 4096) = 4096 >mremap(0xbffb4000, 0x25000, 0x25000, 0x1, 0x25000) = -1 ENOMEM (Cannot allocate memory) >mremap(0xbffb4000, 0x25000, 0x25000, 0x1, 0x25000) = -1 ENOMEM (Cannot allocate memory)
... umm, what?
This particular process obviously (I've traced it before) obviously mremapped a memory block a couple of thousand of times. Every time the kernel moved the block a bit higher. Suddenly it ends up at the upper end of the processes memory space, at which time the kernel forgets to restart at the beginning.
Clues? Patches?
-- Matthias Urlichs noris network GmbH
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |