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

Re: dmalloc and leaks in git

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Dec 9, 2007, 20:57 UTC
Message-ID
<alpine.LFD.0.9999.0712091251330.12046@woody.linux-foundation.org>
In-Reply-To
<9e4733910712081253t7cd43f87o6001f32fddc01565@mail.gmail.com>
On Sat, 8 Dec 2007, Jon Smirl wrote:
> 
> But using dmalloc shows a pervasive problem, none of the git commands
> are cleaning up after themselves. For example I ran a simple command,
> git-status, and thousands of objects were not freed.
One thing to do is to use a better reporting tool.
For example, if you use
	valgrind --tool=massif --heap=yes ...

it will generate a postscript file with the allocation history as a graph of the different allocators in different colors etc. That would likely show where the big users come from..

		Linus
Previous: Johannes SchindelinNext: Linus Torvalds
Message 5 of 7 in “dmalloc and leaks in git”
  1. Jon SmirlDec 8, 2007
  2. Johannes SchindelinDec 8, 2007
  3. Jon SmirlDec 8, 2007
  4. Johannes SchindelinDec 8, 2007
  5. Linus TorvaldsDec 9, 2007
  6. Linus TorvaldsDec 10, 2007
  7. Nicolas PitreDec 10, 2007

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.