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

Re: [PATCH] Reintroduce svn pools to solve the memory leak.

From
Karl Hasselström <kha@treskal.com>
Date
Mar 28, 2006, 12:20 UTC
Message-ID
<20060328122031.GA14124@diana.vm.bytemark.co.uk>
In-Reply-To
<7vhd5joiqt.fsf@assigned-by-dhcp.cox.net>
On 2006-03-27 10:16:58 -0800, Junio C Hamano wrote:
> Karl, were there other reasons you needed to disable the pool here
> (maybe to work around a problem with incompatible version of SVN
> module)? I see some other uses of SVN::Pool still there in the code,
> so I am assuming this was a simple typo, but just in case...

No, it's just a simple mistake (the mistake being me not realizing why an explicit pool was needed, and simply dropping it when things worked fine without it).

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Previous: Jan-Benedict Glaw
Message 4 of 4 in “Reintroduce svn pools to solve the memory leak.”
  1. Reintroduce svn pools to solve the memory leak.Santi Béjar, Mar 27, 2006
  2. Junio C HamanoMar 27, 2006
  3. Jan-Benedict GlawMar 28, 2006
  4. Karl HasselströmMar 28, 2006

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.