Tried to upgrade from 2.2 to 2.3 with Linux 64 bits, however it appears that linux connection pool is not destroyed. I recompiled boost 1.57 and cpprest 2.3.0 with gcc 4.9 (I had to remove "-Werror" in Release/src/CMakeLists.txt) ; works fine with 2.2.0, but not with 2.3.0
How to reproduce :
- add a printf message in ~linux_connection_pool()
- with doc tutorial source code, this message is printed before program exits.
- however, after changing http://www.bing.com to https://www.bing.com and upgrading to 2.3.0, the message does not appear anymore. Moreover valgrind reports a leak.
Note that for both versions 2.2 and 2.3, valgrind emits a lot of errors regarding uninitialized memory in boost::asio ; don't know if they are real errors though.
Comments: Hi momaison, I do agree this bug is significant, but we won't be putting together a special release for it. The only non Windows platform that we produce binaries for right now is Android so you have to build from source. To workaround the issue I temporarily recommend you use the 'development' branch. We are actually planning on trying to do the 2.4.0 release this coming week anyway. Steve
How to reproduce :
- add a printf message in ~linux_connection_pool()
- with doc tutorial source code, this message is printed before program exits.
- however, after changing http://www.bing.com to https://www.bing.com and upgrading to 2.3.0, the message does not appear anymore. Moreover valgrind reports a leak.
Note that for both versions 2.2 and 2.3, valgrind emits a lot of errors regarding uninitialized memory in boost::asio ; don't know if they are real errors though.
Comments: Hi momaison, I do agree this bug is significant, but we won't be putting together a special release for it. The only non Windows platform that we produce binaries for right now is Android so you have to build from source. To workaround the issue I temporarily recommend you use the 'development' branch. We are actually planning on trying to do the 2.4.0 release this coming week anyway. Steve