From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: New features + feature freeze?
Date: 15 Dec 1995 20:14:37 +0100 [thread overview]
Message-ID: <w8spwdqb0ma.fsf@surt.ifi.uio.no> (raw)
In-Reply-To: Wes Hardaker's message of Thu, 14 Dec 1995 13:50:26 -0800
Wes Hardaker <hardaker@ece.ucdavis.edu> writes:
> Ack... I just turned off the icons code and read gnus to see if it
> was my code or gnus that was eating memory. Its gnus.
>
> Lars, have you looked into the variables you create and their size?
> Maybe we should zero out some of the larger ones until the next run?
> Using 'ps' I discovered XEmacs jumped up about 200 memory blocks
> (almost a meg of memory (If I'm getting the block size correctly)).
You mean that XEmacs only grows by 1Mb when you start Gnus? That's
not a lot, in my opinion. Now, if you get 16Mb growth, then I would
be a bit more worried... :-)
But what do you mean by "zero out some of the larger ones"? Zero out
variables?
--
Home is where the cat is.
next prev parent reply other threads:[~1995-12-15 19:14 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-13 18:22 Lars Magne Ingebrigtsen
1995-12-13 19:36 ` Wes Hardaker
1995-12-13 20:05 ` William Perry
1995-12-14 17:52 ` Wes Hardaker
1995-12-15 3:55 ` picons support (was Re: New features + feature freeze?) Ben Gross
1995-12-14 8:29 ` New features + feature freeze? Lars Magne Ingebrigtsen
1995-12-14 17:15 ` Wes Hardaker
1995-12-14 17:27 ` William Perry
1995-12-14 17:36 ` Wes Hardaker
1995-12-14 19:38 ` Lars Magne Ingebrigtsen
1995-12-14 20:49 ` Wes Hardaker
1995-12-15 19:14 ` Lars Magne Ingebrigtsen
1995-12-14 22:39 ` Steven L. Baur
1995-12-15 19:07 ` Lars Magne Ingebrigtsen
1995-12-14 18:25 ` Jens Lautenbacher
1995-12-15 19:14 ` Lars Magne Ingebrigtsen
1995-12-14 19:17 ` Jens Lautenbacher
1995-12-14 20:58 ` Wes Hardaker
1995-12-14 21:50 ` Wes Hardaker
1995-12-15 19:14 ` Lars Magne Ingebrigtsen [this message]
1995-12-15 22:54 ` Wes Hardaker
1995-12-16 16:28 ` Lars Magne Ingebrigtsen
1995-12-14 22:22 ` William Perry
1995-12-14 22:23 ` Wes Hardaker
1995-12-14 9:49 ` Kai Grossjohann
1995-12-14 19:38 ` Lars Magne Ingebrigtsen
1995-12-15 3:07 ` Steven L. Baur
1995-12-15 19:07 ` Lars Magne Ingebrigtsen
1995-12-15 4:02 ` Steven L. Baur
1995-12-15 15:19 ` 守岡 知彦 / MORIOKA Tomohiko
1995-12-15 16:32 ` Wes Hardaker
1995-12-20 2:53 ` Lars Magne Ingebrigtsen
1995-12-15 19:14 ` Lars Magne Ingebrigtsen
1995-12-15 23:51 ` Steven L. Baur
1995-12-16 14:43 ` Lars Magne Ingebrigtsen
1995-12-18 15:55 ` Sten Drescher
1995-12-20 2:53 ` Lars Magne Ingebrigtsen
1995-12-20 14:57 ` Sten Drescher
1995-12-21 3:21 ` Lars Magne Ingebrigtsen
1995-12-21 15:44 ` Sten Drescher
1995-12-22 3:56 ` Christopher Davis
1995-12-22 16:55 ` Sten Drescher
1996-01-03 8:54 ` Lars Magne Ingebrigtsen
1996-01-07 0:16 ` Christopher Davis
1996-01-10 18:37 ` Lars Magne Ingebrigtsen
1996-01-07 1:33 ` Sten Drescher
1996-01-07 7:44 ` Yair Friedman
1996-01-10 18:34 ` Lars Magne Ingebrigtsen
1996-01-12 15:00 ` Per Abrahamsen
1996-01-14 6:08 ` Greg Stark
1996-01-15 23:17 ` Lars Magne Ingebrigtsen
1996-01-10 18:33 ` Lars Magne Ingebrigtsen
1996-01-12 11:31 ` Sten Drescher
1996-01-15 23:17 ` Lars Magne Ingebrigtsen
1996-01-16 7:33 ` Yair Friedman
1996-01-16 18:45 ` Lars Magne Ingebrigtsen
1996-01-16 19:29 ` Yair Friedman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=w8spwdqb0ma.fsf@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).