zsh-workers
 help / color / mirror / code / Atom feed
From: James Kirkpatrick <jimkirk@uwyo.edu>
To: zsh-workers@sunsite.auc.dk
Cc: James Kirkpatrick <jimkirk@uwyo.edu>, Susan L Hanna <hanna@uwyo.edu>
Subject: zsh 3.0.7 hogs memory
Date: Tue, 23 Nov 1999 15:17:26 -0700 (MST)	[thread overview]
Message-ID: <Pine.GSO.4.10.9911231507030.4302-100000@asuwlink.uwyo.edu> (raw)
In-Reply-To: <991123214038.ZM29906@candle.brasslantern.com>

We've run across an interesting problem where zsh 3.0.7 will grow in size,
consuming memory until the system paralyzes itself with swapping, then
suddenly break itself free.

Environment: zsh 3.0.7, Sun Enterprise 5000 with 2 Gig memory and 6
processors, Solaris 2.5.1.

It usually seems to happen to people running Pine (4.10).  My guess at
this point is that they dial in, start pine, and then either disconnect or
become disconnected.  This has often caused problems with programs that
try to handle exceptions and fail in some cases (I've seen this a lot
starting with SAS on Cyber mainframes in 1980).

I tried running a script that sleeps for 1 second then asks "how long have
I been sleeping?".  If the answer is over 2 seconds it does a
"ps -eo pmem,user,pcpu,rss,vsz,fname | sort | tail"
to a log file.  Some of the entries include:

  %MEM     USER %CPU  RSS  VSZ COMMAND
  12.3    hbear  3.1 252832 599944 zsh
  71.3  skuyper  8.1 1466520 1941360 zsh
  86.1    renee 13.2 1772384 1941352 zsh

86% of 2 Gig is 1.72 Gig, a ridiculous amount for a shell to consume, so
clearly there is a problem.

One other clue:  This only started happening when I added the following to
/etc/zshenv:

  export HISTSIZE=200
  export HISTFILE=~/.zsh_history
  export SAVEHIST=200

Once I commented it out, the problem went away.  SO, I'm suspicious of
problems in exception handling (disconnect) with history files turned on.
Of course I might be wrong about the exceptions issue.

Any suggestions/fixes?

Jim


  reply	other threads:[~1999-11-23 22:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-23 18:08 "getopts" bugs and bad interactions with "shift" Bart Schaefer
1999-11-23 18:22 ` Adam Spiers
1999-11-23 21:40   ` Bart Schaefer
1999-11-23 22:17     ` James Kirkpatrick [this message]
1999-11-24  5:35       ` zsh 3.0.7 hogs memory Bart Schaefer
1999-11-24 16:25         ` James Kirkpatrick
1999-11-30 15:42         ` James Kirkpatrick
1999-11-30 16:03           ` Bart Schaefer
1999-11-23 20:36 ` "getopts" bugs and bad interactions with "shift" Zefram

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=Pine.GSO.4.10.9911231507030.4302-100000@asuwlink.uwyo.edu \
    --to=jimkirk@uwyo.edu \
    --cc=hanna@uwyo.edu \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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