Cylix
Sample client deadlocks using vcpkg and Visual Studio 2017
We've heard nothing but good things about this library, so when we needed a Windows client for redis and saw this was supported by vcpkg, we jumped at the chance to use it.
And we were stopped dead in our tracks at the proof-of-concept phase. As every single example that actually tries to communicate with redis deadlocks. (The logger example works just fine,)
Steps to reproduce minimal example:
- Install cpp_redis in vcpkg
- Create brand new solution in VS 2017 - Windows console application - Debug - 64bit
- Gut all the precompiled header stuff
- Cut and paste https://github.com/Cylix/cpp_redis/blob/master/examples/cpp_redis_client.cpp
- Build and run
- Watch the deadlock in tacopie::io_service::thread_pool::stop( ) line 85
We have tried:
Increasing the number of workers via cpp_redis::network::set_default_nb_workers - No impact
Call client.disconnect( false ) - Throws an exception "Microsoft C++ exception: tacopie::tacopie_error at memory location 0x007FF318."
Call client.disconnect( true ) - Changes location of hang to tacopie::io_service::wait_for_removal line 348
During more testing and debugging, we encountered several sparadic, but inconsistent, instances of
f:\dd\vctools\crt\crtw32\stdcpp\thr\mutex.c(51): mutex destroyed while busy
which is mentioned in at least one other open issue.
This appears to be an issue with the version deployed via vcpkg. I cloned the current repository, built it, and the examples work.
Hi,
Sorry for the delayed response. This library does not officially support the vcpkg package, so I am not sure how cpp_redis is available on it, and thus which version is packaged.
I will keep the issue opened though: seems this is not the first time someone request cpp_redis to be available on vcpkg, so better officially support it than leaving a malfunctioned unofficial package out there.
Best
Thank you for the response.
If there is anything I can do to support an official vcpkg, please let me know.