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
Fix win32 memory leak by using raw
file operations
#3906
Conversation
ca58de5
to
a0a8b59
Compare
The commit title is a bit inaccurate as we were already using prim_file which is essentially the same as a raw operation. It would be better to describe that you are using read instead of read_file. |
could the leak be in |
@jhogberg figured it out in record time - erlang/otp#5527 |
@lhoguin I will rewrite the commit message, thanks for pointing that out. |
@kjnilsson that's what I originally thought but it's not the FHC. |
a0a8b59
to
20977f6
Compare
3323b5b
to
365de60
Compare
@lhoguin @michaelklishin I'll re-test this on my Windows system today, then I'll move it out of draft. |
Fix win32 memory leak by using `raw` file operations (backport #3906)
Not ideal but this skips all file servers.