Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:15683 comp.os.386bsd.questions:16917 comp.windows.x:76993 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yoyo.aarnet.edu.au!munnari.oz.au!spool.mu.edu!uwm.edu!lll-winken.llnl.gov!koriel!wnoc-sfc-news!fxmxgw!kspgwy!iwagw!jun From: jun@fox.fax.iwa.fujixerox.co.jp (Junichi Kurokawa) Newsgroups: comp.windows.x.i386unix,comp.os.386bsd.questions,comp.windows.x Subject: does your X grow this huge? leak? Followup-To: comp.windows.x.i386unix Date: 03 Mar 1995 04:28:46 GMT Organization: Fuji Xerox Co., Ltd., Akasaka, Tokyo. Lines: 28 Distribution: world Message-ID: <JUN.95Mar3132846@fox.fax.iwa.fujixerox.co.jp> NNTP-Posting-Host: fox.fax.iwa.fujixerox.co.jp Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII [followups redirected to comp.windows.x.i386unix] I often find my X server grow significantly large, and tend to eat up considerable (subjective) amount of swap space. Currently, I use a precompiled server for S3. [environment] * X311-S3.tgz + Diamond Stealth 64 V-4MB, TrueColor visual * FreeBSD-1.1.5.1 with RAM == 32MB I once saw the X server taking up 22MB in the swap space. Does this happen to you? I know, running a full color screen _is_ heavy on paging, and some other image related programs, notably ImageMagick(1) IMHO just sucks up a darn many number of pages screwing everything up. What can I do to prevent this, if, I were to build a X server by hand? How about linking gnumalloc(3) instead? Regards, junichi -- Junichi Kurokawa Image and Printing System Products Development Center Fuji Xerox Co., Ltd.