Submission of most recent version of lme4 threw a NOTE on CRAN's
Debian platform that we had not seen when running "R CMD check
--as-cran" with the most recent SVN checkout, nor when submitted to
win-builder/R-devel. These are legitimate issues (all now fixed), but
we were taken by surprise
On 22 April 2023 at 14:43, D Z wrote:
| Thank you Dirk and Joshua,
| Using Valgrind, I have found several memory leaks in the program that required
| some smaller rewrites.
| Valgrind (with Makevars flags -O0 and --ggdb) now reports no "definitely" and
| no "indirectly" lost bytes so that's a
Thank you Dirk and Joshua,
Using Valgrind, I have found several memory leaks in the program that required
some smaller rewrites.
Valgrind (with Makevars flags -O0 and --ggdb) now reports no "definitely" and
no "indirectly" lost bytes so that's a small win already.
But two questions remain:
