-
Notifications
You must be signed in to change notification settings - Fork 228
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
There's a memory leak problem in Curl::Easy.download #240
Comments
This path would probably fix it but since the current master segfault on my laptop I will not create a pull request
|
Thanks for finding this definitely looks like a bug... and your patch makes good sense. looking into why it is now causing a segfault in your example |
Do you have a sample test case I can run to repeat the crash? |
I believe this is fixed now in 0.9.0 please confirm. |
As I can see it's not fixed
puts "MEMORY USAGE: %d MB" % (`ps -o rss= -p #{Process.pid}`.to_i / 1024)
=> MEMORY USAGE: 107 MB
Curl::Easy.download(direct_link_to_large_file)
puts "MEMORY USAGE: %d MB" % (`ps -o rss= -p #{Process.pid}`.to_i / 1024)
=> MEMORY USAGE: 139 MB in my case file size was 32MB which is eq to difference in memory, so, I suppose it's been loaded into memory somewhere. I experimented with file on our corporate s3, so, can't share direct link here. |
I use the following code.
And it quickly (about 50M/s) eats up my memory.
The text was updated successfully, but these errors were encountered: