{"thread":{"id":"2378","subject":"HTTP push","startedAt":"2005-11-07T02:35:33Z","lastAt":"2005-11-07T04:31:49Z","messageCount":2,"participants":["Johannes Schindelin","Nick Hengeveld"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"11240","messageId":"Pine.LNX.4.63.0511070328230.25684@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2378","inReplyTo":null,"subject":"HTTP push","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-11-07T02:35:33Z","receivedAt":"2005-11-07T02:35:33Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nI played a little with git-http-push. There are some strange things going \non: whenever I commented out the calls to curl_multi_remove_handle() and \ncurl_multi_cleanup(), all was well. Whenever I did not, there was either a \nsegfault, or an endless loop.\n\nAlso, I had to update my curl, because http-push *absolutely* needs \nCURLOPT_HTTPGET. I tried to fake it with any combination of \nCURLOPT_{NOBODY,POST,PUT,UPLOAD}, but failed. (Yes, that means that you \nwon't have to deal any longer with my patches to support older curl \nversions...)\n\nNote: all my tests are from an iBook (client) to an Intel Linux (server).\n\nI will run some tests on another client with valgrind (that will wait \nuntil tomorrow; it's 3.30am local time, so I head to bed).\n\nCiao,\nDscho\n"},{"id":"11243","messageId":"20051107043149.GH3001@reactrix.com","threadId":"2378","inReplyTo":"Pine.LNX.4.63.0511070328230.25684@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: HTTP push","fromName":"Nick Hengeveld","fromEmail":"nickh@reactrix.com","sentAt":"2005-11-07T04:31:49Z","receivedAt":"2005-11-07T04:31:49Z","isPatch":false,"sender":{"key":"nickh@reactrix.com","avatar":null},"body":"On Mon, Nov 07, 2005 at 03:35:33AM +0100, Johannes Schindelin wrote:\n\n> I played a little with git-http-push. There are some strange things going \n> on: whenever I commented out the calls to curl_multi_remove_handle() and \n> curl_multi_cleanup(), all was well. Whenever I did not, there was either a \n> segfault, or an endless loop.\n\nhttp-push is a bit more aggressive than http-fetch about freeing up memory,\nperhaps too aggressive...  I ran into similar issues when memory was\nfreed more than once.\n\n> I will run some tests on another client with valgrind (that will wait \n> until tomorrow; it's 3.30am local time, so I head to bed).\n\nThanks, I'll work on memory cleanup some more.\n\n-- \nFor a successful technology, reality must take precedence over public\nrelations, for nature cannot be fooled.\n"}]}