From: Kip Macy <kip.macy@gmail.com>
To: Matt Mackall <mpm@selenic.com>
Cc: xen-devel@lists.xensource.com, mercurial@selenic.com,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: [Xen-devel] hg 0.7 released
Date: Tue, 20 Sep 2005 18:19:57 -0700 [thread overview]
Message-ID: <b1fa2917050920181915a246f0@mail.gmail.com> (raw)
In-Reply-To: <20050921011435.GA21777@waste.org>
[-- Attachment #1.1: Type: text/plain, Size: 2219 bytes --]
Hmm -
What are you doing differently in 0.7 that is causing the server to use more
memory?
-Kip
On 9/20/05, Matt Mackall <mpm@selenic.com> wrote:
>
> On Tue, Sep 20, 2005 at 06:07:34PM -0700, Kip Macy wrote:
> > nifty - but 0.7 is not backward compatible with 0.6b:
> > %hg clone http://xenbits.xensource.com/xen-unstable.hg
> > requesting all changes
> > adding changesets
> > adding manifests
> > adding file changes
> > added 6917 changesets with 0 changes to 0 files
> > ** unknown exception encountered, details follow
> > ** report bug details to mercurial@selenic.com
>
> Not so hasty. The bug is in fact that xenbits is sometimes running out
> of memory. Other times it works just fine. Here are the relevant bits
> from my diagnosis this morning:
>
> ----
>
> And then I added exception handling to the pull code, so that it now
> does this:
>
> abort: premature EOF reading chunk (got 75478 bytes, expected
> 1651992944)!
>
> That expected number says there's probably something else in the
> stream. Firing up Ethereal and tracing a connection shows:
>
> <!-- The above is a description of an error in a Python program,
> formatted
> for a Web browser because the 'cgitb' module was enabled. In
> case you
> are not reading this in a Web browser, here is the original
> traceback:
>
> Traceback (most recent call last):
> File "/var/www/html/xen-unstable.hg", line 9, in ?
> h.run()
> File "/usr/local/hg-0.6c/lib/python/mercurial/hgweb.py", line 701,
> in run
> chunk = f.read(4096)
> File "/usr/local/hg-0.6c/lib/python/mercurial/hg.py", line 1442, in
> read
> self.buf += self.g.next()
> File "/usr/local/hg-0.6c/lib/python/mercurial/hg.py", line 1469, in
> gengroup
> for y in self.manifest.group(linkmap): yield y
> File "/usr/local/hg-0.6c/lib/python/mercurial/revlog.py", line 433,
> in group
> chunks[r] = decompress(data[pos: pos + l])
> File "/usr/local/hg-0.6c/lib/python/mercurial/revlog.py", line 33,
> in decompress
> if t == 'x': return zlib.decompress(bin)
> MemoryError
>
> -->
>
> So the server ran out of memory trying to decompress a manifest.
>
> --
> Mathematics is the supreme nostalgia of our time.
>
[-- Attachment #1.2: Type: text/html, Size: 3128 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
Mercurial mailing list
Mercurial@selenic.com
http://selenic.com/mailman/listinfo/mercurial
next prev parent reply other threads:[~2005-09-21 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 21:28 hg 0.7 released Hollis Blanchard
2005-09-21 1:07 ` Kip Macy
2005-09-21 1:14 ` [Xen-devel] " Matt Mackall
2005-09-21 1:19 ` Kip Macy [this message]
2005-09-21 1:27 ` Matt Mackall
2005-09-21 1:32 ` Kip Macy
2005-09-21 13:28 ` James Bulpin
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=b1fa2917050920181915a246f0@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=hollisb@us.ibm.com \
--cc=mercurial@selenic.com \
--cc=mpm@selenic.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.