public inbox for
 help / color / mirror / Atom feed
From: "john at starfire dot" <>
Subject: [Bug bzip2/26264] New: hangs on compression of large httpd-error.log file
Date: Sun, 19 Jul 2020 16:18:02 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 26264
           Summary: hangs on compression of large httpd-error.log file
           Product: bzip2
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: bzip2
          Assignee: nobody at sourceware dot org
          Reporter: john at starfire dot
                CC: bzip2-devel at sourceware dot org
  Target Milestone: ---

I am running version 1.0.8 on FreeBSD on a Raspberry PI 3 Plus (arm64).  Things
start out just fine, but then all of a sudden, the output file quits growing
and one of the CPU cores is 100% consumed by bzip2.  I have waited several
minutes, and it just doesn't seem to progress any farther.  The filesystem is
only 21% full and no errors are posted to messages.

If desired, I can submit the log file causing the problem - but it's 138Mb so I
don't want to do that unless necessary.

FreeBSD 12.1-RELEASE r354233 GENERIC  arm64

You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-07-19 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19 16:18 john at starfire dot [this message]
2020-07-19 22:25 ` [Bug bzip2/26264] " mark at klomp dot org
2021-04-11 15:12 ` vapier at gentoo dot org
2022-05-26 20:06 ` mark at klomp dot org

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).