Error in memory.size(size) when calling R in batch mode (but not in interactive mode)
Thank you for the hint. In batch mode, I got: R version 2.15.1 (2012-06-22) Platform: i386-pc-mingw32/i386 (32-bit) In interactive mode, I got: R version 2.15.1 (2012-06-22) Platform: x86_64-pc-mingw32/x64 (64-bit) And I have found the cause. In my path, I had still included C:\R-2.15.1\bin\i386 (I had copied an old batch file, and overlooked this). The problem is solved now. -----Original Message----- From: Milan Bouchet-Valat [mailto:nalimilan at club.fr] Sent: vrijdag 9 november 2012 14:34 To: Franckx Laurent Cc: 'r-help at r-project.org' Subject: Re: [R] Error in memory.size(size) when calling R in batch mode (but not in interactive mode) Le vendredi 09 novembre 2012 ? 10:43 +0000, Franckx Laurent a ?crit :
Dear all
I use a 64 bit Windows7 system with 16 GB memory.
I have run an R script in batch mode with the following command:
R CMD BATCH masterassignment_2012_11_09.r --save The execution
was terminated with the following error message:
Error in memory.size(size) : don't be silly!: your machine
has a 4Gb address limit
I never get this error message in an interactive session (and I don't
think I should, taking into account the system). To be sure, I have
just double checked this again in an interactive session, and it works
fine.
There are two possible explanations I can think of:
a) The command line doesn't "know" the system, i.e. it "thinks" it
works on a 32bit system (is this possible at all?)
b) I run R on a remote desktop, and the command line thinks I am
calling R from my laptop
c) When you run "R CMD BATCH", the 32-bit version of R is used, while when you run it interactively, you start the 64-bit version. To check this, add sessionInfo() to your batch script, and have a look at the output. Hope this helps
Anyway, I wouldn't know how to solve this. In case you wonder why I run R in batch mode at all: I have a series of iterations in my model, each of which is taking huge amount of memory. Although I regularly impose a garbage collection, after two or three iterations, R crashes when used interactively. I thought that running and exiting R after each iteration would be the only effective way to "clean up" memory. If you have any other solutions, I would be happy to hear about them as well. Laurent Franckx, PhD VITO NV Boeretang 200, 2400 MOL, Belgium Tel. + 32 14 33 58 22 Skype: laurent.franckx laurent.franckx at vito.be Visit our website: www.vito.be/english and http://www.vito.be/transport
________________________________ [http://www.vito.be/e-maildisclaimer/bsds.png] <http://bsds.vito.be> VITO Disclaimer: http://www.vito.be/e-maildisclaimer ______________________________________________ R-help at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
________________________________ [http://www.vito.be/e-maildisclaimer/bsds.png] <http://bsds.vito.be> VITO Disclaimer: http://www.vito.be/e-maildisclaimer