Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.windows.x Frequently Asked Questions (FAQ) 7/7
Section - 152) Why does the process size of my X programs go up,up,up?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Schools ]


Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 151) Is this a memory leak in the X11R4 deletion of work procs?!
Next Document: 153) Are callbacks guaranteed to be called in the order registered?
See reader questions & answers on this topic! - Help others by sharing your knowledge

Using "ps" may not show any decrease in memory size after a malloc/free pair. 
With most vendors' implementations of memory managers, the call to free does 
not return memory to the operating system; it is probably maintained on a free 
list for the process. In addition, ps may not be an accurate report of current
memory usage requirements.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



Top Document: comp.windows.x Frequently Asked Questions (FAQ) 7/7
Previous Document: 151) Is this a memory leak in the X11R4 deletion of work procs?!
Next Document: 153) Are callbacks guaranteed to be called in the order registered?

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
faq%craft@uunet.uu.net (X FAQ maintenance address)




Last Update March 27 2014 @ 02:12 PM