From: Nick Hengeveld <nickh@reactrix.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: HTTP push
Date: Sun, 6 Nov 2005 20:31:49 -0800 [thread overview]
Message-ID: <20051107043149.GH3001@reactrix.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511070328230.25684@wbgn013.biozentrum.uni-wuerzburg.de>
On Mon, Nov 07, 2005 at 03:35:33AM +0100, Johannes Schindelin wrote:
> I played a little with git-http-push. There are some strange things going
> on: whenever I commented out the calls to curl_multi_remove_handle() and
> curl_multi_cleanup(), all was well. Whenever I did not, there was either a
> segfault, or an endless loop.
http-push is a bit more aggressive than http-fetch about freeing up memory,
perhaps too aggressive... I ran into similar issues when memory was
freed more than once.
> I will run some tests on another client with valgrind (that will wait
> until tomorrow; it's 3.30am local time, so I head to bed).
Thanks, I'll work on memory cleanup some more.
--
For a successful technology, reality must take precedence over public
relations, for nature cannot be fooled.
prev parent reply other threads:[~2005-11-07 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 2:35 HTTP push Johannes Schindelin
2005-11-07 4:31 ` Nick Hengeveld [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=20051107043149.GH3001@reactrix.com \
--to=nickh@reactrix.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).