Re: [PATCH 2/7] sequencer: release a strbuf used in save_head()
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- May 22, 2012, 05:18 UTC
- Message-ID
- <20120522051827.GA4486@burratino>
- In-Reply-To
- <CALkWK0kvjr3NSx6-8svz=PKb5ta_UwOUiF4uqh7GriwuJYncUA@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Jonathan Nieder wrote:
Show 8 quoted lines
>> And >> looking at it from the other side, doesn't using exit mean that you >> cannot be valgrind-clean anyway, since allocations by functions higher >> in the call chain do not get a chance to be freed? > > Good point; save_todo() sets a bad example. For symmetry, should > these two instances of strbuf_release() before die() be removed in a > separate patch?
I can't find myself caring much either way. :)
A single free() doesn't hurt performance much, so my hunch would be to leave it alone unless some other practical reason to keep or remove the free()s comes up.