On Monday 31 May 2004 3:03 pm, Orlando Andico wrote: > On Mon, 31 May 2004, bopolissimus X platypus wrote:
> the brk() / sbrk() system call WILL NOT RELEASE MEMORY until the process > exits. So even if malloc() memory is free()'ed by the process, the actual > RSS WILL NOT GET REDUCED. it's really the behavior of the underlying > system calls which do memory allocation. > > anyway the huge RSS you may note is mostly swapped out. yes it is (swapped out). however, the computer gets slow as the RSS grows. it slows down clearly because of swapping (the drive light continually lights up just as the computer gets slow). so enough of it gets swapped in that it makes the computer noticeably slower. now, if the RSS grows to ridiculous sizes, it seems to me that there's something wrogn either with the memory allocator (it's asking for more memory from the system when there is probably still memory available in the heap, or it's fragmenting its heap too much and can't find large free blocks and has to ask for more memory), or there's a memory leak in evolution. but then, i haven't gone to google yet to see if anyone else is whining about evolution memory usage :-). i'll do that next. tiger -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
