This bug can still be reproduced in an easy and consistent manner. I've attached a script reproducing the leaks. It simply spins up a swift SAIO box in vagrant, and then runs the curl command mentioned in this issue. Every time the script is run, more memory is leaked. If the proxy-server is restared, the memory will be freed.
A small note: while the script was provisioning the vagrant box for the first time, apt failed. This was easily fixed:
$ cd vagrant-swift-all-in-one/
$ vagrant ssh -c "sudo apt-get -f install -y"
$ vagrant provision
Then just rerun the script:
$ cd ..
$ ./leakreproducer.sh
This bug can still be reproduced in an easy and consistent manner. I've attached a script reproducing the leaks. It simply spins up a swift SAIO box in vagrant, and then runs the curl command mentioned in this issue. Every time the script is run, more memory is leaked. If the proxy-server is restared, the memory will be freed.
A small note: while the script was provisioning the vagrant box for the first time, apt failed. This was easily fixed: swift-all- in-one/
$ cd vagrant-
$ vagrant ssh -c "sudo apt-get -f install -y"
$ vagrant provision
Then just rerun the script:
$ cd ..
$ ./leakreproducer.sh