From: John (_You_ hide, they seek.) Mackin <john@physiol.su.oz.au>
To: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: memory leaks
Date: Thu, 13 Aug 1992 00:32:01 -0400 [thread overview]
Message-ID: <199208131432.12476.rc.babef@physiol.su.oz.au> (raw)
In-Reply-To: <92Aug12.220812edt.2680@groucho.cs.psu.edu>
Scott says his rc leaks memory on interrupts. Like Byron, I can't duplicate
this. Scott, could it be a startup thing? Don't forget that rc, quite
legitimately, grows at first when you do things. That's not a leak,
because it doesn't _keep_ growing when you _keep_ doing them. As Byron
pointed out to me at one stage:
--- begin included message
From: Byron Rakitzis <byron@archone.tamu.edu>
Date: Thu, 27 Jun 1991 01:33:33 -0500
To: john@syd.dit.csiro.au
Subject: Re: rc memory leaks
Received: from ARCHONE.TAMU.EDU by ditsydh.syd.dit.csiro.au with SMTP id AA17099
(5.64+/IDA/DIT-0.9 for john); Thu, 27 Jun 91 16:33:56 +1000
Received: by archone.tamu.edu id <22531>; Thu, 27 Jun 1991 01:33:45 -0500
Message-Id: <91Jun27.013345cdt.22531@archone.tamu.edu>
Re: sun rc growing slowly. I find that when I start up a copy of rc and
type a few things at it, it grows. However, the real test for a memory
leak is to type the same command 1000 times. Does the shell grow in this
case?
(of course, you don't type the same command 1000 times, you . a file with
the command written out 1000 times)
[...]
--- end included message
I tried this with 1.4. Do a ps l of your rc, then in another window
(to avoid observer effect) run "for (x in `{seq 1000}) kill -2 <the-pid>".
Do another ps. It doesn't grow.
How do you reproduce it, Scott?
OK,
John.
next prev parent reply other threads:[~1992-08-13 4:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-08-13 2:08 Scott Schwartz
1992-08-13 4:32 ` John Mackin [this message]
1992-08-13 7:56 ` Scott Schwartz
1992-08-13 10:30 ` Mark-Jason Dominus
1992-08-13 3:44 Byron Rakitzis
1992-08-13 7:28 ` Scott Schwartz
1992-08-13 13:34 Chet Ramey
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=199208131432.12476.rc.babef@physiol.su.oz.au \
--to=john@physiol.su.oz.au \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).