git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/6] Memory leaks once again
@ 2015-03-27 22:09 Stefan Beller
  2015-03-27 22:09 ` [PATCH 1/6] pack-bitmap: fix a memleak Stefan Beller
                   ` (10 more replies)
  0 siblings, 11 replies; 12+ messages in thread
From: Stefan Beller @ 2015-03-27 22:09 UTC (permalink / raw)
  To: git, gitster; +Cc: Stefan Beller

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

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2015-03-27 22:12 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-27 22:09 [PATCH 0/6] Memory leaks once again Stefan Beller
2015-03-27 22:09 ` [PATCH 1/6] pack-bitmap: fix a memleak Stefan Beller
2015-03-27 22:09 ` [PATCH 1/6] shallow: " Stefan Beller
2015-03-27 22:09 ` [PATCH 2/6] line-log.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 2/6] shallow: " Stefan Beller
2015-03-27 22:09 ` [PATCH 3/6] line-log.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 4/6] " Stefan Beller
2015-03-27 22:09 ` [PATCH 4/6] wt-status.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 5/6] pack-bitmap: " Stefan Beller
2015-03-27 22:09 ` [PATCH 5/6] wt-status.c: " Stefan Beller
2015-03-27 22:09 ` [PATCH 6/6] WIP/RFC/entry.c: " Stefan Beller
2015-03-27 22:12 ` [PATCH 0/6] Memory leaks once again Stefan Beller

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).