Yegappan wrote:
> Running the latest Vim under valgrind reports the following memory leak:
>
> ==608== 2 bytes in 2 blocks are definitely lost in loss record 2 of 27
> ==608==at 0x4A06A2E: malloc (vg_replace_malloc.c:270)
> ==608==by 0x4F2DAA: lalloc (misc2.c:976)
> ==608==by
Yegappan Lakshmanan wrote:
> Running the test_matchstrpos.vim test under valgrind reports a
> small memory leak in the find_some_match() function. The attached
> patch fixes this leak.
Thanks!
--
Due knot trussed yore spell chequer two fined awl miss steaks.
/// Bram Moolenaar --
Yegappan Lakshmanan wrote:
> Valgrind detected a memory leak in the ex_vimgrep() function when running
> the Test_nomem() function in the test_quickfix.vim file. The attached patch
> fixes this leak.
Thanks.
Glad to see that adding this kind of test can locate problems.
--
Normal people
Dimitar wrote:
1. valgrind --leak-check=full --show-reachable=yes ./vim -u NONE -U NONE
2. ZQ
==14191== LEAK SUMMARY:
==14191==definitely lost: 36 bytes in 1 blocks.
==14191==indirectly lost: 120 bytes in 10 blocks.
==14191== possibly lost: 0 bytes in 0 blocks.
==14191==
On 09/07/10 00:26, Dimitar DIMITROV wrote:
valgrind --leak-check=full --show-reachable=yes gvim
1. cc, then a,a,a,a,a,a,a,a,a,a,a,
2. /\(\(\s*\w\+\s*\)\+,\)\{1,20}
3. :h\{
4. Close gvim
==3987== LEAK SUMMARY:
==3987== definitely lost: 12,986 bytes in 47 blocks.
==3987== indirectly lost: 28,332
On Thu, Jul 8, 2010 at 6:55 PM, Tony Mechelynck wrote:
If you want to usefully contribute memory leak reports, please use the
latest version, either the latest stable version (currently 7.2.445) or the
bleeding-edge development version (7.3a, available only over Mercurial, not
as a bz2
On 10/7/07, Tony Mechelynck [EMAIL PROTECTED] wrote:
It's not clear to me what memory is leaked (if any is really leaked,
valgrind may give a false warning). When I put this line before syntax
on it appears to disappear:
let g:vimembedscript= 0
So it's related to :syn
Dominique Pelle wrote:
vim seems to be leaking memory when doing :so % with syntax on setting.
Steps to reproduce:
1/ create a simple script as follows:
$ cat leak.vim
leaks memory when doing :so % while this file is loaded in vim
syntax on
2/ start vim
$ valgrind
Bram Moolenaar wrote:
Dominique Pelle wrote:
vim seems to be leaking memory when doing :so % with syntax on setting.
Steps to reproduce:
1/ create a simple script as follows:
$ cat leak.vim
leaks memory when doing :so % while this file is loaded in vim
syntax on
2/ start vim
$
