This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
> I've applied the patch but in general we should avoid adding much code > to free memory in case allocation fails. Maybe to free some huge blocks > but not more. If the app runs out of memory it'll very soon terminate. > No need to bloat the code to help doing this. I disagree completely. It is important that library code never leak. It very well might be used in server situations where allocations can fail at maximum load, or with unreasonable client input, but then enough more memory gets freed by cleaning up resources associated with clients as they die, that the server need never die.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |