From owner-freebsd-current Mon Aug 24 03:03:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28611 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:03:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maks.bhg.ru (dialup-29186.dialup.ptt.ru [195.34.29.186] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28600 for ; Mon, 24 Aug 1998 03:03:36 -0700 (PDT) (envelope-from ramax@maks.bhg.ru) Received: from news (ramax.maks.ru [10.0.0.4]) by maks.bhg.ru (8.8.5/8.8.5) with SMTP id OAA00991 for ; Mon, 24 Aug 1998 14:00:51 GMT Date: Mon, 24 Aug 1998 14:02:13 +0400 From: =?Windows-1251?B?zODq8ejsINDg5eLx6ujpIA==?= =?Windows-1251?B??= X-Mailer: The Bat! (v1.020) S/N 35751953 Reply-To: =?Windows-1251?B?zODq8ejsINDg5eLx6ujpIA==?= =?Windows-1251?B??= Organization: MAKS Message-ID: <1584.980824@maks.bhg.ru> To: freebsd-current@FreeBSD.ORG Subject: Re: encountered possible VM bug ? References: <19980824111923.A207@compufit.at> Mime-Version: 1.0 Content-Type: text/plain; charset=Windows-1251 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Alexander, AS> I'am running -current (dated 08/17) on a PPro/200, Gigabyte MB, 128 M. AS> Ok, what happened ? AS> While I was playing with the KDE newsreader (krn), I encountered a bug AS> in krn, probably caused by some kind of infinite recursion or similar. AS> Fact is, while krn tried to "thread" a group, it started to eat memory AS> like crazy. After a while, I noticed quite a bit swapping. I checked AS> ps, and found out that krn has allocated more than 160 MB (!!) of RAM AS> (I have 128 physical, about 100 MB swap). I assume, that the overall AS> memory consumtion of the system must have been somewhere around 200 MB AS> at this time. I was running X, full KDE desktop; a Netscape session and AS> a copy of gimp were active on another desktop aswell). However, I AS> managed to kill -9 the crazy krn app, and everything seemed to be ok. AS> The only message I found in the log is: AS> Aug 24 01:53:05 darkstar /kernel: swap_pager: suggest more swap space: 254 MB AS> Next time, I tried to connect to my local newsserver (nntpd, handled by AS> inetd), I got an error. I telnet'ed to port 119 and got something like AS> "realloc() junk pointer, too low" as an error message from inetd. AS> I had to kill and restart inetd to restore normal operation. AS> What the hell happened to inetd ? AS> BTW: no other problems occured so far; system is still up and running. I am following KDE mailing lists. There was a mention of a memory leak in KDE, confirmed (as fat as I understood) by the programmers. So keep calm, it's not FreeBSD-related To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message