summaryrefslogtreecommitdiff
path: root/builtin/stash.c
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2020-08-18 22:58:25 (GMT)
committerJunio C Hamano <gitster@pobox.com>2020-08-19 00:17:29 (GMT)
commitdad4f23ce59339bb32ad9e1cc1682c696f7a724f (patch)
tree44a55aa6e9c91af202fecd8887a7c175f1db3aa6 /builtin/stash.c
parent2befe97201e1f3175cce557866c5822793624b5a (diff)
downloadgit-dad4f23ce59339bb32ad9e1cc1682c696f7a724f.zip
git-dad4f23ce59339bb32ad9e1cc1682c696f7a724f.tar.gz
git-dad4f23ce59339bb32ad9e1cc1682c696f7a724f.tar.bz2
dir: make clear_directory() free all relevant memory
The calling convention for the dir API is supposed to end with a call to clear_directory() to free up no longer needed memory. However, clear_directory() didn't free dir->entries or dir->ignored. I believe this was an oversight, but a number of callers noticed memory leaks and started free'ing these. Unfortunately, they did so somewhat haphazardly (sometimes freeing the entries in the arrays, and sometimes only free'ing the arrays themselves). This suggests the callers weren't trying to make sure any possible memory used might be free'd, but just the memory they noticed their usecase definitely had allocated. Fix this mess by moving all the duplicated free'ing logic into clear_directory(). End by resetting dir to a pristine state so it could be reused if desired. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/stash.c')
-rw-r--r--builtin/stash.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/builtin/stash.c b/builtin/stash.c
index 10d8763..da48533 100644
--- a/builtin/stash.c
+++ b/builtin/stash.c
@@ -875,11 +875,8 @@ static int get_untracked_files(const struct pathspec *ps, int include_untracked,
strbuf_addstr(untracked_files, ent->name);
/* NUL-terminate: will be fed to update-index -z */
strbuf_addch(untracked_files, '\0');
- free(ent);
}
- free(dir.entries);
- free(dir.ignored);
clear_directory(&dir);
return found;
}