git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: HTTP push

From
NHNick Hengeveld <nickh@reactrix.com>
Date
Nov 7, 2005, 04:31 UTC
Message-ID
<20051107043149.GH3001@reactrix.com>
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.
Previous: Johannes Schindelin
Message 2 of 2 in “HTTP push”
  1. Johannes SchindelinNov 7, 2005
  2. Nick HengeveldNov 7, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.