From csr21 at cantab.net  Thu Jul 21 20:53:09 2011
From: csr21 at cantab.net (Christophe Rhodes)
Date: Thu, 21 Jul 2011 19:53:09 +0100
Subject: [Rd] --max-vsize
Message-ID: <87sjpzlb3e.fsf@cantab.net>

Hi,

In both R 2.13 and the SVN trunk, I observe odd behaviour with the
--max-vsize command-line argument:

1. passing a largeish value (about 260M or greater) makes mem.limits()
   report NA for the vsize limit; gc() continues to report a value...

2. ...but that value (and the actual limit) is wrong by a factor of 8.

I attach a patch for issue 2, lightly tested.  I believe that fixing
issue 1 involves changing the return convention of do_memlimits -- not
returning a specialized integer vector, but a more general numeric; I
wasn't confident to do that.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-src-main-memory.c-set-R_MaxVSize-when-assigning-to-v.patch
Type: text/x-diff
Size: 824 bytes
Desc: fix --max-vsize command-line argument
URL: <https://stat.ethz.ch/pipermail/r-devel/attachments/20110721/3faef1b7/attachment.bin>
-------------- next part --------------

Please let me know if there's anything else I can do.

Best,

Christophe


[Rd] --max-vsize
Christophe Rhodes