From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Felix Rosencrantz <f_rosencrantz@yahoo.com>, zsh-workers@sunsite.dk
Subject: Re: Occasional 'job table full or recursion limit exceeded'
Date: Sun, 1 Sep 2002 16:28:50 +0000 [thread overview]
Message-ID: <1020901162850.ZM18601@candle.brasslantern.com> (raw)
In-Reply-To: <20020828073146.91195.qmail@web10409.mail.yahoo.com>
On Aug 28, 12:31am, Felix Rosencrantz wrote:
} Subject: Occasional 'job table full or recursion limit exceeded'
}
} There are times I will see the following error in my long running active
} shells:
} _description:70: job table full or recursion limit exceeded
}
} My job table is not full.
The message is slightly misleading. Many built-in shell constructs (such
as "while" and other loops) allocate job table entries even when running
in the current shell, for purposes of simulated signal handling (e.g., so
you can stop the entire loop with ^Z). That's what the "recursion limit"
part is talking about.
Since much of the completion system is implemented as nested loops over
the set of tags, the set of possible matches, etc., it's conceivable that
some completions are running out of job table entries. The size of the
table is only 50 unless `configure --enable-max-jobtable-size' is used,
and (having seen a number of _complete_debug call traces) I can believe
that you'd reach that.
We should probably consider increasing the default MAXJOB value.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-09-01 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 7:31 Felix Rosencrantz
2002-09-01 16:28 ` Bart Schaefer [this message]
2002-09-02 9:47 ` Peter Stephenson
2002-09-02 9:52 ` Peter Stephenson
2002-09-04 6:32 I've committed "zargs" Bart Schaefer
2002-09-09 14:41 ` Occasional 'job table full or recursion limit exceeded' Felix Rosencrantz
2002-09-09 16:22 ` Bart Schaefer
2002-09-11 10:36 ` Felix Rosencrantz
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=1020901162850.ZM18601@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=f_rosencrantz@yahoo.com \
--cc=zsh-workers@sunsite.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).