-
Notifications
You must be signed in to change notification settings - Fork 555
Sample client deadlocks using vcpkg and Visual Studio 2017 #184
Comments
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
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. 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.
|
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:
The text was updated successfully, but these errors were encountered: