Noticed while working on the stress tests. A unit test checks that 128 Mb startup parameter is picked up, but it seems that ~2GB is the max that R native accepts, even on a 64 bits windows box.
Workaround - using memory.limit() to at least have the --max-size option taken up.
Tried to use cmdlineoptions , but this is coupled to RTerm/RGui.
Comments: The last few release should let you use more than 2GB, i.e. pick up the startup parameter correctly. From a user's point of view this should be fixed. Basically I am calling memory.limit() at the end of the R engine initialisation procedure, so you should not need to worry about this. Open an issue if you have some persisting problems of course. The details I wrote were more for me to have a written trace of the oddities of the R embedding API and internals so that I or someone else do not have to rediscover this.
Workaround - using memory.limit() to at least have the --max-size option taken up.
Tried to use cmdlineoptions , but this is coupled to RTerm/RGui.
Comments: The last few release should let you use more than 2GB, i.e. pick up the startup parameter correctly. From a user's point of view this should be fixed. Basically I am calling memory.limit() at the end of the R engine initialisation procedure, so you should not need to worry about this. Open an issue if you have some persisting problems of course. The details I wrote were more for me to have a written trace of the oddities of the R embedding API and internals so that I or someone else do not have to rediscover this.