New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unlet v:["count"]
leaks memory
#1497
Comments
Leak log itself:
|
ZyX-I
added a commit
to ZyX-I/neovim
that referenced
this issue
Feb 20, 2017
ZyX-I
added a commit
to ZyX-I/neovim
that referenced
this issue
Feb 23, 2017
chrisbra
pushed a commit
to chrisbra/vim
that referenced
this issue
Mar 25, 2017
Problem: Unlet command leaks memory. (Nikolai Pavlov) Solution: Free the memory on error. (closes vim#1497)
desvp
pushed a commit
to desvp/vim
that referenced
this issue
May 30, 2017
Problem: Unlet command leaks memory. (Nikolai Pavlov) Solution: Free the memory on error. (closes vim#1497)
ckelsel
added a commit
to ckelsel/neovim
that referenced
this issue
Mar 17, 2018
Problem: Unlet command leaks memory. (Nikolai Pavlov) Solution: Free the memory on error. (closes vim/vim#1497) vim/vim@49439c4
justinmk
pushed a commit
to neovim/neovim
that referenced
this issue
Mar 17, 2018
Problem: Unlet command leaks memory. (Nikolai Pavlov) Solution: Free the memory on error. (closes vim/vim#1497) vim/vim@49439c4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce the leak it is enough to compile Vim with address sanitizing enabled (without disabling memory leak detection) and running
vim -i NONE -u NONE --cmd 'unlet v:["count"]' --cmd cq
(actually, any DI_FLAGS_RO variable should do, I initially found this when creating test suite for my version of b:changedtick patch).The text was updated successfully, but these errors were encountered: