"out of memory" error

[Sean]

Bram> Please report every problem you find! The time until a 7.2
release
Bram> depends on how many problems are reported.

(I did post by clicking Reply, but it never showed up. Fortunately, I
used vim to edit, so I have a copy :))

I don't think vim72b (or vim72a, patch 1-19) is stable, as I can see
"out of memory" error more than once per day on my Windows XP. The
gvim.exe I used was compiled using the default "make -f Make_cyg.mak".

In comparison, the gvim.exe (vim71) is stable, because I could only
find "out of memory" error around once every two weeks.

I have been using gvim.exe on daily basis, and I have not changed my
configuration (_vimrc, vimfiles, etc) for a while.

I tried to reproduce the error, but it seemed not easy. It looks false
alarm because a same file can be opened without error after another
click.

Most errors looked like the following format:
Out of memory! (allocating {number} bytes)
and it sometimes points to certain line in $VIMRUNTIME/filetype.vim.

I am wondering if I am the only one who saw those frustrated errors?

Thanks

Sean

[Tony Mechelynck]

Strange that filetype.vim would produce OOM errors. I think it would
help if you could report at which line(s) the error happens.

Best regards,
Tony.
--
Lowery's Law:
If it jams -- force it. If it breaks, it needed replacing
anyway.

[Markus Heidelberg]

Sean, 14.07.2008:

>
> I don't think vim72b (or vim72a, patch 1-19) is stable, as I can see
> "out of memory" error more than once per day on my Windows XP. The
> gvim.exe I used was compiled using the default "make -f Make_cyg.mak".
>
> In comparison, the gvim.exe (vim71) is stable, because I could only
> find "out of memory" error around once every two weeks.
>

> I am wondering if I am the only one who saw those frustrated errors?

I also have this error at work on Windows XP gvim71. It occurs very rarely,
perhaps about 5 times in the last half year. It only occured directly after
starting Vim, at the next start everything went fine.

I'm not sure, but I think I haven't seen this error before switching to a more
recent 7.1 version. Currently I'm using 7.1.242 from Cream without Cream. The
version before was 7.1.0 from vim.org I think.

Markus