> On Saturday, December 12, 2020, 6:33:33 PM EST, Ben Bolker > <bbol...@gmail.com> wrote: > > On Windows you can use memory.limit. > > https://stackoverflow.com/questions/12582793/limiting-memory-usage-in-r-under-linux > > Not sure how much that helps. > >On 12/12/20 6:19 PM, Arne Henningsen wrote: >> When working with a huge data set with character string variables, I >> experienced that various commands let R crash. When I run R in a >> Linux/bash console, R terminates with the message "Killed". When I use >> RStudio, I get the message "R Session Aborted. R encountered a fatal >> error. The session was terminated. Start New Session". If an object in >> the R workspace needs too much memory, I would expect that R would not >> crash but issue an error message "Error: cannot allocate vector of >> size ...". A minimal reproducible example (at least on my computer) >> is: >> >> nObs <- 1e9 >> >> date <- paste( round( runif( nObs, 1981, 2015 ) ), round( runif( nObs, >> 1, 12 ) ), round( runif( nObs, 1, 31 ) ), sep = "-" ) >> >> Is this a bug or a feature of R?
On OS X I see: > nObs <- 1e9 > date <- paste( round( runif( nObs, 1981, 2015 ) ), round( runif( nObs,1, 12 ) ), round( runif( nObs, 1, 31 ) ), sep = "-" ) Error: vector memory exhausted (limit reached?) > sessionInfo() R version 4.0.3 (2020-10-10) Platform: x86_64-apple-darwin17.0 (64-bit) Running under: macOS Catalina 10.15.7 Which is what I would expect. I don't doubt the error you've seen, just providing a data point for whoever ends up looking into this further. Best, Brodie. ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
