* using log directory 'd:/Rcompile/CRANpkg/local/4.4/DarkDiv.Rcheck'
* using R version 4.4.0 (2024-04-24 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'DarkDiv/DESCRIPTION' ... OK
* checking extension type ... Package
* this is package 'DarkDiv' version '0.3.0'
* package encoding: UTF-8
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking whether package 'DarkDiv' can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... [2s] OK
* checking whether the package can be loaded with stated dependencies ... [1s] OK
* checking whether the package can be unloaded cleanly ... [2s] OK
* checking whether the namespace can be loaded with stated dependencies ... [2s] OK
* checking whether the namespace can be unloaded cleanly ... [2s] OK
* checking loading without being on the library search path ... [2s] OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [7s] OK
* checking Rd files ... [0s] OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... WARNING
Fatal error: couldn't allocate node stack

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
Error: cannot allocate vector of size 2.2 Mb
Call sequence:
11: (function (n) 
    {
        if (existsInFrame(n, envenv)) 
            envenv[[n]]
        else {
            e <- mkenv()
            envenv[[n]] <- e
            key <- env[[n]]
            ekey <- if (is.list(key)) 
                key$eagerKey
            else key
            data <- lazyLoadDBfetch(ekey, datafile, compressed, envhook)
            parent.env(e) <- data$enclos %||% emptyenv()
            list2env(data$bindings, e)
            if (!is.null(data$attributes)) 
                attributes(e) <- data$attributes
            if (!is.null(data$isS4) && data$isS4) 
                .Internal(setS4Object(e, TRUE, TRUE))
            if (is.list(key)) {
                expr <- quote(lazyLoadDBfetch(KEY, datafile, compressed, 
                    envhook))
                .Internal(makeLazy(names(key$lazyKeys), key$lazyKeys, 
                    expr, parent.env(environment()), e))
            }
            if (!is.n
Execution halted
The \usage entries for S3 methods should use the \method markup and not
their full name.
See chapter 'Writing R documentation files' in the 'Writing R
Extensions' manual.
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... WARNING
Fatal error: couldn't allocate node stack

* checking LazyData ... NOTE
  'LazyData' is specified without a 'data' directory
* checking examples ... ERROR
Running massageExamples to create 'DarkDiv-Ex.R' failed

 NONE
* checking PDF version of manual ... [0s] WARNING
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
* checking PDF version of manual without index ... ERROR
Re-running with no redirection of stdout/stderr.
* checking HTML version of manual ... [1s] OK
* DONE
Status: 2 ERRORs, 3 WARNINGs, 1 NOTE