Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Os.freemem() under Windows #27386

Closed
morgan-wild opened this issue Apr 24, 2019 · 4 comments
Closed

Os.freemem() under Windows #27386

morgan-wild opened this issue Apr 24, 2019 · 4 comments
Labels
invalid Issues and PRs that are invalid. os Issues and PRs related to the os subsystem. windows Issues and PRs related to the Windows platform.

Comments

@morgan-wild
Copy link

  • Version: 10.15.3 (LTS)
  • Platform: Windows 10
  • Subsystem: Os.freemem()

Under Windows, Os.freemem() returns the used memory instead of the free one.

@himself65
Copy link
Member

it's okay on v12.0.0

@tniessen
Copy link
Member

I cannot reproduce that in node 10.15.3 on Windows 10. (Sorry that the screenshot is in German.)

screenshot

Node.js uses uv_get_free_memory internally, so if this is an issue at all, it might be in libuv. libuv uses GlobalMemoryStatusEx and MEMORYSTATUSEX.ullAvailPhys which should work.

@nanixne
Copy link

nanixne commented Apr 24, 2019

I can not reproduce this issue on node 12.0.0 windows 10 english version.

@bnoordhuis
Copy link
Member

Closing. OP didn't follow up and no one can reproduce. It also simply sounds unlikely.

@bnoordhuis bnoordhuis added invalid Issues and PRs that are invalid. os Issues and PRs related to the os subsystem. windows Issues and PRs related to the Windows platform. labels Apr 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid Issues and PRs that are invalid. os Issues and PRs related to the os subsystem. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests

5 participants