From owner-freebsd-current Mon Aug 24 02:29:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24948 for freebsd-current-outgoing; Mon, 24 Aug 1998 02:29:11 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.psa.at (uvo1-42.univie.ac.at [131.130.231.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24942 for ; Mon, 24 Aug 1998 02:29:06 -0700 (PDT) (envelope-from root@darkstar.psa.at) Received: (from root@localhost) by darkstar.psa.at (8.8.8/8.8.8) id LAA00238 for freebsd-current@freebsd.org; Mon, 24 Aug 1998 11:19:24 +0200 (CEST) (envelope-from root) Message-ID: <19980824111923.A207@compufit.at> Date: Mon, 24 Aug 1998 11:19:23 +0200 From: Alexander Sanda To: freebsd-current@FreeBSD.ORG Subject: encountered possible VM bug ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Operating-System: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'am running -current (dated 08/17) on a PPro/200, Gigabyte MB, 128 M. Ok, what happened ? While I was playing with the KDE newsreader (krn), I encountered a bug in krn, probably caused by some kind of infinite recursion or similar. Fact is, while krn tried to "thread" a group, it started to eat memory like crazy. After a while, I noticed quite a bit swapping. I checked ps, and found out that krn has allocated more than 160 MB (!!) of RAM (I have 128 physical, about 100 MB swap). I assume, that the overall memory consumtion of the system must have been somewhere around 200 MB at this time. I was running X, full KDE desktop; a Netscape session and a copy of gimp were active on another desktop aswell). However, I managed to kill -9 the crazy krn app, and everything seemed to be ok. The only message I found in the log is: Aug 24 01:53:05 darkstar /kernel: swap_pager: suggest more swap space: 254 MB Next time, I tried to connect to my local newsserver (nntpd, handled by inetd), I got an error. I telnet'ed to port 119 and got something like "realloc() junk pointer, too low" as an error message from inetd. I had to kill and restart inetd to restore normal operation. What the hell happened to inetd ? BTW: no other problems occured so far; system is still up and running. -- # /AS/ http://privat.schlund.de/entropy/ # # # # XX has detected, that your mouse cursor has changed position. Please # # restart XX, so it can be updated. -- From The Gimp manual # To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message