All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Steven Grimm <koreth@midwinter.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH (WIP)] git-svn: cache SVN::Ra functions in a more Perl GC-friendly way
Date: Tue, 24 Apr 2007 23:40:53 -0700	[thread overview]
Message-ID: <20070425064053.GA4310@muzzle> (raw)
In-Reply-To: <462D544C.8010206@midwinter.com>

Steven Grimm <koreth@midwinter.com> wrote:
> FYI, with this patch, it actually dies more often. The stack seems to be 
> corrupted so I can't give you a useful stack trace, but here's what gdb 
> says:

Yikes.

Thanks for the feedback.  Sorry, I've still been busy with another big
project and haven't been able to track down this nasty bug.

If somebody wants to take a stab at working around it: hack up a patch
that forks a new child (reusing the main connection) for every revision
it needs to fetch.  It should still be as fast as normal on *nix
machines because fork() is fast and it won't have to renegotiate the
connection in every child, but memory leaks and corruption won't have a
chance to accumulate.

-- 
Eric Wong

  reply	other threads:[~2007-04-25  6:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 22:17 Segmentation fault in git-svn Steven Grimm
2007-04-17  9:37 ` Eric Wong
2007-04-17  9:40   ` [PATCH (WIP)] git-svn: cache SVN::Ra functions in a more Perl GC-friendly way Eric Wong
2007-04-24  0:50     ` Steven Grimm
2007-04-25  6:40       ` Eric Wong [this message]
2007-04-17  9:55   ` Segmentation fault in git-svn Eric Wong
2007-04-18  9:01     ` Eric Wong
2007-04-19 21:31       ` [RFH] " Eric Wong
2007-05-03 12:35 ` Peter Baumann
2007-05-13  8:21   ` Eric Wong
2007-05-13 22:04     ` Steven Grimm
2007-05-14  9:02       ` Peter Baumann

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=20070425064053.GA4310@muzzle \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=koreth@midwinter.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.