===========================================================
                                      .___ __  __   
          _________________  __ __  __| _/|__|/  |_ 
         / ___\_` __ \__  \ |  |  \/ __ | | \\_  __\
        / /_/  >  | \// __ \|  |  / /_/ | |  ||  |  
        \___  /|__|  (____  /____/\____ | |__||__|  
       /_____/            \/           \/           
              grep rough audit - static analysis tool
                  v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
r-cran-profmem-0.5.0+dfsg/inst/doc/profmem.md.rsp-61-From this, we find that <%= p$bytes[1] %> bytes are allocated for integer vector `x`, which is because each integer value occupies 4 bytes of memory.  The additional 40 bytes are due to the internal data structure used for each variable R.  The size of this allocation can also be confirmed by the value of `object.size(x)`.
r-cran-profmem-0.5.0+dfsg/inst/doc/profmem.md.rsp:62:We also see that `rnorm()`, which is called via `matrix()`, allocates <%= p$bytes[2] %> + <%= p$bytes[3] %> bytes, where the first one reflects the <%= length(Y) %> double values each occupying 8 bytes.  The second one reflects some unknown allocation done internally by the native code that `rnorm()` uses.
r-cran-profmem-0.5.0+dfsg/inst/doc/profmem.md.rsp-63-Finally, the following entry reflects the memory allocation of <%= p$bytes[4] %> bytes done by `matrix()` itself.
##############################################
r-cran-profmem-0.5.0+dfsg/vignettes/profmem.md.rsp-61-From this, we find that <%= p$bytes[1] %> bytes are allocated for integer vector `x`, which is because each integer value occupies 4 bytes of memory.  The additional 40 bytes are due to the internal data structure used for each variable R.  The size of this allocation can also be confirmed by the value of `object.size(x)`.
r-cran-profmem-0.5.0+dfsg/vignettes/profmem.md.rsp:62:We also see that `rnorm()`, which is called via `matrix()`, allocates <%= p$bytes[2] %> + <%= p$bytes[3] %> bytes, where the first one reflects the <%= length(Y) %> double values each occupying 8 bytes.  The second one reflects some unknown allocation done internally by the native code that `rnorm()` uses.
r-cran-profmem-0.5.0+dfsg/vignettes/profmem.md.rsp-63-Finally, the following entry reflects the memory allocation of <%= p$bytes[4] %> bytes done by `matrix()` itself.
##############################################
r-cran-profmem-0.5.0+dfsg/debian/tests/run-unit-test-5-if [ "$AUTOPKGTEST_TMP" = "" ] ; then
r-cran-profmem-0.5.0+dfsg/debian/tests/run-unit-test:6:    AUTOPKGTEST_TMP=`mktemp -d /tmp/${debname}-test.XXXXXX`
r-cran-profmem-0.5.0+dfsg/debian/tests/run-unit-test-7-    trap "rm -rf $AUTOPKGTEST_TMP" 0 INT QUIT ABRT PIPE TERM