rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: John Mackin (_You_ hide, they seek.) <john@physiol.su.oz.au>
Cc: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: memory leaks
Date: Thu, 13 Aug 1992 03:56:05 -0400	[thread overview]
Message-ID: <92Aug13.035614edt.2686@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Thu, 13 Aug 92 00:32:01 EDT." <199208131432.12476.rc.babef@physiol.su.oz.au>


| Scott says his rc leaks memory on interrupts.  Like Byron, I can't duplicate
| this.  

Hmmm.  Maybe there is something system specific involved?  I tested
it on a sparc2 with gcc 2.2.2.

| Scott, could it be a startup thing?

I don't think so.  It grows on every ^C.  One of the typescripts I just
posted starts with an empty environment; no prompt function or other
junk.

| 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.

Hmmm.  It just did for me:

Script started on Thu Aug 13 03:45:18 EDT 1992
; ps v26812
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26812 q1 I     0:00 41 99      0   96  340    xx  0.0  2.3 rc
; kill -2 26812
; ps v26812
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26812 q1 S     0:00  3 99      0   96  344    xx  0.0  2.3 rc
; kill -2 26812
; ps v26812
  PID TT STAT  TIME SL RE PAGEIN SIZE  RSS   LIM %CPU %MEM COMMAND
26812 q1 S     0:00  5 99      0  100  344    xx  0.0  2.3 rc
; Script done on Thu Aug 13 03:45:56 EDT 1992



  reply	other threads:[~1992-08-13  7:56 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
1992-08-13  7:56   ` Scott Schwartz [this message]
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=92Aug13.035614edt.2686@groucho.cs.psu.edu \
    --to=schwartz@groucho.cs.psu.edu \
    --cc=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).