Hi Peng,
in a very simplistic manner, what happens is that the Operating System
"thinks" it is too dangerous to let the R process to use so much
memory. So, to protect the whole system, it kills R, before the system
becomes unstable.
I've been looking at the problem you observed last week and, as I
promised, I will come back to you with my findings sometime this week.
I was already informed on how to reduce the memory footprint when
creating the specific object you're interested in, but still need to
run some tests.
Will get back to you soon,
b
On Nov 10, 2009, at 2:23 PM, Peng Yu wrote:
2009/11/10 Uwe Ligges <lig...@statistik.tu-dortmund.de>:
Peng Yu wrote:
My R process has been killed for a few times, although the system
administrator did not do so. It happened when R attempted to
allocate
a lot of memory. I'm wondering whether R would spontaneously kill
itself if it can not allocate enough memory?
It does not kill itself. If it was not some out-of-memory kill
process of
your OS, then you may have seen some segfault. We need reproducible
code and
all the details described in the posting guide.
Please see this thread about the necessary information.
http://www.mail-archive.com/r-help@r-project.org/msg74804.html
______________________________________________
R-help@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.
______________________________________________
R-help@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.
