Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!psuvax1!rutgers!columbia!cs!swfc From: swfc@mendelssohn.cs.columbia.edu (Shu-Wie F Chen) Newsgroups: comp.sys.next Subject: Re: swapfile size and hanging Message-ID: Date: 15 Nov 89 15:11:14 GMT References: <6934@pt.cs.cmu.edu> Sender: news@cs.columbia.edu Distribution: usa Organization: Columbia University Computer Science Lines: 37 In-reply-to: avie@wb1.cs.cmu.edu's message of 11 Nov 89 02:46:20 GMT >In article swfc@mendelssohn.cs.columbia.edu (Shu-Wie F Chen) writes: >> >>My NeXT machine has been hanging recently. It seems that my swapfile grows >>to my high watermark of 80Mbytes and then thrashes(?) to death. >> >>What's going on? > >Yes, your machine is thrashing to death. You must be running some program >with a severe memory leak (unfortunately, virtual memory systems tend to >allow these to run for long times). If you notice your swapfile is large, >launch a Shell and try something like "ps aux" Look under the VSIZE column >(virtual size) for processes with huge virtual sizes. What to do next will >depend on what you find. >-- >Avadis Tevanian, Jr. (Avie) >Manager, System Software >NeXT, Inc. >avie@NeXT.COM Well, we have found the program with the severe memory leak. It seems to be lookupd. Currently, it has a VSIZE of 45.5M, up from 40M of three hours ago. This "phenomena" has also been observed on another NeXT. I had been told by jgreely that this is YP-related and is a known problem. 1. What is the bug/problem 2. When will it be fixed 3. Is there a temporary fix besides rebooting every couple of days or not running YP Thanks. ~swfc ------------------------------------------------------------------------------- Shu-Wie F Chen Department of Computer Science swfc@cs.columbia.edu Columbia University