From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: [9fans] 9pserv leaking?
Date: Sat, 1 Oct 2005 14:24:06 -0500 [thread overview]
Message-ID: <20051001192406.AF94D14E533@dexter-peak.quanstro.net> (raw)
; ps auxwww | grep 9pserv
quanstro 4432 0.0 0.4 137036 1140 tty1 Sl Sep17 0:42 9pserve -u unix!/tmp/ns.quanstro.:0/plumb
quanstro 19386 0.2 0.2 84180 760 pts/32 Sl 14:09 0:00 9pserve -u unix!/tmp/ns.quanstro.:0/acme
quanstro 19453 0.0 0.1 1524 500 pts/4 S+ 14:10 0:00 grep 9pserv
i looked into this the other day, but didn't get very far.
the only thing i did notice is that in sendq() the allocated
bytes for the Qel* are not freed if q->hungup:
int
sendq(Queue *q, void *p)
{
Qel *e;
e = emalloc(sizeof(Qel));
qlock(&q->lk);
if(q->hungup){
werrstr("hungup queue");
qunlock(&q->lk);
return -1;
}
[...]
any ideas?
erik
next reply other threads:[~2005-10-01 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 19:24 erik quanstrom [this message]
2005-10-02 14:52 ` Russ Cox
2005-10-05 12:17 ` erik quanstrom
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=20051001192406.AF94D14E533@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.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).