Re: Bug Report?! Part II.
Craig Sanders <email@example.com> writes:
> that sounds like a memory leak, OR a program which just needs more
> memory than you have OR both.
Right. He should look for some allocation that he's not freeing. I
would suspect he's seeing swapping rather than file caching.
> also, rethink your algorithm - do you REALLY need to have the entire
> file loaded into memory at once, or can you process it line-by-line? if
> you want to load the entire file into memory then OF COURSE it is going
> to use memory, how can it not do so?
Also, if he needs the whole file in memory at the same time, he could
investigate mmap which would at least keep the file data from adding
to the swapping load...
Rob Browning <firstname.lastname@example.org> PGP=E80E0D04F521A094 532B97F5D64E3930