It would never make sense for such messages to reflect normal and expected operation, so hypothesizing about intentionally changing stack behavior doesn't make sense.
The default format for saveRDS changed in 3.6.0. There may be bugs associated with that, but rolling back to 3.6.0 would just trade bugs. https://cran.r-project.org/doc/manuals/r-devel/NEWS.html On July 16, 2019 8:56:28 PM CDT, Jan Galkowski <bayesianlogi...@gmail.com> wrote: >Did something seriously change in R 3.6.1 at least for Windows in terms >of stack impacts? > >I'm encountering many problems with the 00UNLOCK, needing to disable >locking during installations. > >And I'm encountering > >> Error: C stack usage 63737888 is too close to the limit > >for cases I did not before, even when all I'm doing is serializing an >object to be saved with *saveRDS* or even *save.image(.)*. > >Yes, I know, I did not append a minimally complete example. Just wanted >to see if it was just me, or if anyone else was seeing this. > >It's on Windows 7 HE and I've run *R* here for years. > >My inclination is to drop back to 3.6.0 if it is just me or if no one >knows about this problem. > >Thanks, > > - Jan Galkowski. > > > [[alternative HTML version deleted]] > >______________________________________________ >R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see >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. -- Sent from my phone. Please excuse my brevity. ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see 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.
