On Mi, 16 Dez 2015, Mike Williams wrote:
> I have checked 4789 with upped maxmem and it worked, and checked the
> previous change - 4787 with reduced maxmem and that failed. So the
> issue is interaction of maxmem with the example process for
> reproducing the corruption. I would imagine this means the issue
> can be forced on other systems as well and not just Windows.
Yes I think it should now be reproducible on other systems as well.
That's why I mentioned the exact settings in my previous mail.
[HAVE_AVAIL_MEM]
> However, it does throw out the setting of maxmem/maxmemtot with it.
> The setting of maxmem/maxmemtot should be under a separate control
> IMHO.
Yes that I thought as well.
I remember when I debugged the blowfish corruption bug on Windows I
wondered why the maxmem/maxmemtot setting was so much lower than on
Linux. I wanted to suggest increasing that setting on Windows as well,
but forgot about it.
Best,
Christian
--
Politik wird mit dem Kopf, nicht mit dem Kehlkopf gemacht.
-- Franz Josef Strauß
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
