commit: discard partial cache before (re-)reading it
The read_cache() in prepare_to_commit() would end up clobbering the pointer we had for a previously populated "the_index.cache_tree" in the very common case of "git commit" stressed by e.g. the tests being changed here. We'd populate "the_index.cache_tree" by calling "update_main_cache_tree" in prepare_index(), but would not end up with a "fully prepared" index. What constitutes an existing index is clearly overly fuzzy, here we'll check "active_nr" (aka "the_index.cache_nr"), but our "the_index.cache_tree" might have been malloc()'d already. Thus the code added in11c8a74a64
(commit: write cache-tree data when writing index anyway, 2011-12-06) would end up allocating the "cache_tree", and would interact here with code added in7168624c35
(Do not generate full commit log message if it is not going to be used, 2007-11-28). The result was a very common memory leak. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Taylor Blau <me@ttaylorr.com>
This commit is contained in:

committed by
Junio C Hamano

parent
ab2cf37183
commit
03267e8656
@ -987,8 +987,11 @@ static int prepare_to_commit(const char *index_file, const char *prefix,
|
||||
struct object_id oid;
|
||||
const char *parent = "HEAD";
|
||||
|
||||
if (!active_nr && read_cache() < 0)
|
||||
die(_("Cannot read index"));
|
||||
if (!active_nr) {
|
||||
discard_cache();
|
||||
if (read_cache() < 0)
|
||||
die(_("Cannot read index"));
|
||||
}
|
||||
|
||||
if (amend)
|
||||
parent = "HEAD^1";
|
||||
|
Reference in New Issue
Block a user