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

[PATCH 0/6] Memory leaks once again

From
Stefan Beller <sbeller@google.com>
Date
Mar 27, 2015, 22:09 UTC
Message-ID
<1427494150-8085-1-git-send-email-sbeller@google.com>

Here comes another bunch of memory leaks fixed. patches 1-4 are safe bets, but 5 and 6 are not so.

In patch 5 I wonder if we need to fix more aggressively and in patch 6 I just know there is a leak but I have no idea how to actually fix it.

Stefan Beller (6):
  shallow: fix a memleak
  line-log.c: fix a memleak
  line-log.c: fix a memleak
  wt-status.c: fix a memleak
  pack-bitmap: fix a memleak
  WIP/RFC/entry.c: fix a memleak
 entry.c       |  4 +++-
 line-log.c    |  4 ++++
 pack-bitmap.c | 27 ++++++++++++++++++---------
 shallow.c     |  4 ++--
 wt-status.c   |  2 ++
 5 files changed, 29 insertions(+), 12 deletions(-)
-- 
2.3.0.81.gc37f363
Next: Stefan Beller
Message 1 of 12 in “Memory leaks once again”
  1. 0/6 Memory leaks once againStefan Beller, Mar 27, 2015
  2. 1/6 pack-bitmap: fix a memleakStefan Beller, Mar 27, 2015
  3. 1/6 shallow: fix a memleakStefan Beller, Mar 27, 2015
  4. 2/6 line-log.c: fix a memleakStefan Beller, Mar 27, 2015
  5. 2/6 shallow: fix a memleakStefan Beller, Mar 27, 2015
  6. 3/6 line-log.c: fix a memleakStefan Beller, Mar 27, 2015
  7. 4/6 line-log.c: fix a memleakStefan Beller, Mar 27, 2015
  8. 4/6 wt-status.c: fix a memleakStefan Beller, Mar 27, 2015
  9. 5/6 pack-bitmap: fix a memleakStefan Beller, Mar 27, 2015
  10. 5/6 wt-status.c: fix a memleakStefan Beller, Mar 27, 2015
  11. 6/6 WIP/RFC/entry.c: fix a memleakStefan Beller, Mar 27, 2015
  12. Stefan BellerMar 27, 2015

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.