From: "erik quanstrom" <quanstro@quanstro.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>,
"Russ Cox" <rsc@swtch.com>
Subject: Re: [9fans] 9pserv leaking?
Date: Wed, 5 Oct 2005 07:17:50 -0500 [thread overview]
Message-ID: <20051005121750.C26FEECC99@dexter-peak.quanstro.net> (raw)
In-Reply-To: <ee9e417a0510020752k2286a636xbb2d0aa1af9e40ce@mail.gmail.com>
russ,
sorry about the delay in answering but i've been pretty busy and i thought
that i'd suffered a brain fart. i /thought/ i saw that the size of 9pserve
was 137M not 137k, as the email seems to indicate. (ps seems to be confused.)
however, i found the core today and it's nearly 190M. it grew 45M in
the two hrs i was away from my computer before i sent gdb after it.
what should i be looking at in this core?
erik
Russ Cox <rsc@swtch.com> writes
|
| > ; 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
|
| This isn't convincing that there's a memory leak.
| Maybe you've just had more simultaneous messages
| outstanding than acme connections. I on the other
| hand run a lot of wins all the time, so my acme 9pserve is
| bigger.
|
| rsc 4410 09:32 0:00 732K Sleep 9pserve -u unix!/tmp/ns.x40/factotum
| rsc 4506 09:32 0:00 772K Sleep 9pserve -u unix!/tmp/ns.x40/plumb
| rsc 4560 09:32 0:15 904K Sleep 9pserve -u unix!/tmp/ns.x40/acme
|
| I tried to reproduce this using plumber but can't find anything:
|
prev parent reply other threads:[~2005-10-05 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 19:24 erik quanstrom
2005-10-02 14:52 ` Russ Cox
2005-10-05 12:17 ` erik quanstrom [this message]
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=20051005121750.C26FEECC99@dexter-peak.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).