On 06/20/2013 01:55 PM, Jeff King wrote: > On Thu, Jun 20, 2013 at 09:49:51AM +0200, Michael Haggerty wrote: > >> [I just noticed that lock_ref_sha1_basic() leaks a struct lock_file >> every time that it is called.] > > I noticed that recently, too. I have a patch series about 90% complete > that abstracts the tempfile handling (the ultimate goal of which is to > optionally clean up tmp_* files in the objects/ directory). It refactors > the lockfile cleanup, and it would not be too hard to have a committed > or rolled-back lockfile actually remove itself from the "to clean at > exit" list. > > Which would make it perfectly safe to have a lockfile as an automatic > variable as long as you commit or rollback before leaving the function.
Cool, then I won't work on that. You might also have to make the lockfile list into a doubly-linked-list to avoid having to do a linear scan to find the entry to delete, unless the total number of entries is known to remain small. Please CC me on the patch series when it is done. Michael -- Michael Haggerty mhag...@alum.mit.edu http://softwareswirl.blogspot.com/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
