> You didn't tell us much about your memory usage patterns.
> Do you allocate large lots of large objects and then
> free them? That would explain the larger footprint
> and the identical umem. Do you agree with the second
> allocation profile?
i should have included this information.
the way i
You didn't tell us much about your memory usage patterns.
Do you allocate large lots of large objects and then
free them? That would explain the larger footprint
and the identical umem. Do you agree with the second
allocation profile?
It is easily possible that aux/acidleak's bitmap code
is not
i have a process (modified upas/fs) that has quite a large amount
of allocation churn. on startup, its memory footprint looks like this:
quanstro 63050:00 0:00 6264K Pread8.out
umem reports this
73023 4673712 henter+0x8e
2435 702224 newmessage+0x16
2434
