From owner-freebsd-stable Tue Oct 27 22:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24760 for freebsd-stable-outgoing; Tue, 27 Oct 1998 22:32:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles237.castles.com [208.214.165.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24754 for ; Tue, 27 Oct 1998 22:32:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00939; Tue, 27 Oct 1998 22:31:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810280631.WAA00939@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brenton Vandepeer cc: freebsd-stable@FreeBSD.ORG Subject: Re: Excessive memory consumption with gnuplot In-reply-to: Your message of "Wed, 28 Oct 1998 15:19:35 +1030." <3636A25F.A9EBE88C@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Oct 1998 22:31:46 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here's the story (see kern/8473): > > Invoking gnuplot 3.5 under FreeBSD 2.2.7-STABLE causes excessive > consumption of memory when displaying data. The problem seems to > occur above some threshold in input data file size. For example, > input data files above about 1 Mb sometimes give rise to 150 - > 200 Mb of swap being consumed. One data file tested with a size > of 3 Mb caused ~400 Mb of swap to be consumed. This problem is not > repeatable under 3.0-RELEASE, or another OS tested (linex 2.0.0) Which malloc is/are your gnuplot binaries linked against? Use ldd `which gnuplot` to get a library listing (presuming it's not linked statically). If you take the binary from the 2.2 system and run it on the 3.0 system, does it exhibit the 2.2 or 3.0 behavior? Did you build the gnuplot binaries from the ports collection or were they package installs? Which version(s) of gnuplot are you running? The behaviour you're describing is typical of pathalogically bad malloc() interaction; it's fairly uncommon to see this with the FreeBSD malloc, which is why I ask which one(s) you're using. (There haven't been significant changes to the libc malloc for over a year now.) The contents of /proc//map would also be interesting to see (where is the process ID of the offending gnuplot process). How's the brewing going? Made up for the dent you must have made a few weeks back? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message