In mono, if a thread from the thread pool uses the REngine, several errors about a limited stack size appear. This is described in section 8.1.5 of http://cran.r-project.org/doc/manuals/R-exts.pdf
One option is to disable the thread checking as described there, or check the stack size in .NET
Comments: Hi, Release 1.5.11 uses a lock for preserve/unpreserve operations, and this seems to enable multi-threading, and more importantly prevent things going seriously pear-shaped when creating/disposing R objects at a fast pace. I still seemed to get these "C stack too close to the limit errors" on a Debian box, but this may have been when things were going "seriously pear shaped" in my stress tests.
One option is to disable the thread checking as described there, or check the stack size in .NET
Comments: Hi, Release 1.5.11 uses a lock for preserve/unpreserve operations, and this seems to enable multi-threading, and more importantly prevent things going seriously pear-shaped when creating/disposing R objects at a fast pace. I still seemed to get these "C stack too close to the limit errors" on a Debian box, but this may have been when things were going "seriously pear shaped" in my stress tests.