This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
process.memoryUsage() always returns zero values
#563
Comments
kfarnung
added a commit
that referenced
this issue
Jul 8, 2018
* New worker and ES modules tests * New zlib test that depends on `process.memoryUsage()` Refs: #563
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jul 24, 2018
* New worker and ES modules tests * New zlib test that depends on `process.memoryUsage()` Refs: nodejs#563
kfarnung
added a commit
to kfarnung/node-chakracore
that referenced
this issue
Jul 25, 2018
* New worker and ES modules tests * New zlib test that depends on `process.memoryUsage()` Refs: nodejs#563
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A test was added that depends on
process.memoryUsage()to verify memory growth. It depends on V8 APIs and seems to always return zero currently.When this is fixed reenable:
parallel/test-zlib-unused-weakThe text was updated successfully, but these errors were encountered: