Hi,
Here is test project on problems reported in blogpost http://kostylizm.blogspot.ru/2014/05/run-r-code-from-c-sharp.html
Error messages we had in production:
Version 1.5.5:
Error: C stack usage is too close to the limit
In addition: Warning messages:
1: package 'xts' was built under R version 3.0.3
2: package 'rugarch' was built under R version 3.0.3
A first chance exception of type 'RDotNet.ParseException' occurred in RDotNet.dll
Version 1.5.11
at RDotNet.REngine.Parse(String statement, StringBuilder incompleteStatement)
at RDotNet.REngine.<Defer>c__Iterator4.MoveNext()
at System.Linq.Enumerable.LastOrDefault[TSource](IEnumerable`1 source)
at RDotNet.REngine.Evaluate(String statement)
In attached project reproduced only second.
Run method ParallelRFromRNetTest
Hope will help resolve problem.
Comments: I think I understand the issue. I have a test that quickly reproduces this issue, and a change in the engine init procedure does seem to make a difference between things working or not. Basically, a call to `SetDangerousInt32("R_CStackLimit", -1)` was done on Linux but not Windows (not sure why; maybe not enough multi-threading non-concurrent error reports). Fixed release coming soon.
Here is test project on problems reported in blogpost http://kostylizm.blogspot.ru/2014/05/run-r-code-from-c-sharp.html
Error messages we had in production:
Version 1.5.5:
Error: C stack usage is too close to the limit
In addition: Warning messages:
1: package 'xts' was built under R version 3.0.3
2: package 'rugarch' was built under R version 3.0.3
A first chance exception of type 'RDotNet.ParseException' occurred in RDotNet.dll
Version 1.5.11
at RDotNet.REngine.Parse(String statement, StringBuilder incompleteStatement)
at RDotNet.REngine.<Defer>c__Iterator4.MoveNext()
at System.Linq.Enumerable.LastOrDefault[TSource](IEnumerable`1 source)
at RDotNet.REngine.Evaluate(String statement)
In attached project reproduced only second.
Run method ParallelRFromRNetTest
Hope will help resolve problem.
Comments: I think I understand the issue. I have a test that quickly reproduces this issue, and a change in the engine init procedure does seem to make a difference between things working or not. Basically, a call to `SetDangerousInt32("R_CStackLimit", -1)` was done on Linux but not Windows (not sure why; maybe not enough multi-threading non-concurrent error reports). Fixed release coming soon.