public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Brian Inglis <Brian.Inglis@Shaw.ca>
Cc: Linux Man-Pages <linux-man@vger.kernel.org>,
	Alejandro Colomar <alx.manpages@gmail.com>,
	Deri <deri@chuzzlewit.myzen.co.uk>
Subject: Re: man-pages-posix: POSIX book build
Date: Sun, 13 Aug 2023 17:29:42 -0500	[thread overview]
Message-ID: <20230813222942.tyu75xmsnfokonbg@illithid> (raw)
In-Reply-To: <4c6d1cd6-7b25-2818-108d-5af7afaa9680@Shaw.ca>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hi Brian,

At 2023-08-13T15:04:03-0600, Brian Inglis wrote:
> When I ran the perl script, eqn was growing into the GB memory, and
> eqn and troff were each hogging a cpu, so I left it running while we
> were out at dinner with friends, but *eqn* died after apparently
> exhausting all memory and using 48GB page space, getting as far as
> limits.h(0p) for a 57 page PDF!

Gack.  If this was GNU troff, please report it officially.

https://savannah.gnu.org/bugs/?group=groff&func=additem

Please attach the offending exhibit and any script(s) necessary to drive
the issue.  If you have time to truncate the input to the page after
limits.h(0p), and the bug reproduces, that would be helpful.

I only know of one other issue like this, but it has nothing to do with
eqn, and it tarpits every *roff it meets.

https://savannah.gnu.org/bugs/index.php?64229

But eqn itself doesn't create or use diversions (it can't--it's already
exited by the time a "diversion" exists), so at first blush I think
something else must be making it go asymptotic.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2023-08-13 22:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 21:04 man-pages-posix: POSIX book build Brian Inglis
2023-08-13 21:17 ` Alejandro Colomar
2023-08-13 22:29 ` G. Branden Robinson [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=20230813222942.tyu75xmsnfokonbg@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=alx.manpages@gmail.com \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=linux-man@vger.kernel.org \
    /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