CryptoCurrencyStuff

I seem to have run into a similar issue when spawning many async requests from js ws client: namely a bad this pointer in get_message. Thread 11 "provablyfair_ga" received signal...

`#0` 0x00000000004aea9d in websocketpp::connectionwebsocketpp::config::asio::send ( op=websocketpp::frame::opcode::text, payload="{\"roll\":{\"success\":true,\"nonce\":5,\"roll\":909,\"target\":1998,\"condition_high\":true,\"amount\":1.000000,\"profit\":-1.000000,\"balance\":1000.249200}}", this=0x7fffe40307b0) at /home/ebola/Projects/ProvablyFair/libprovablyfair/../../websocketpp/websocketpp/impl/connection_impl.hpp:86 #1 websocketpp::endpointwebsocketpp::connection::send (ec=, op=websocketpp::frame::opcode::text, payload="{\"roll\":{\"success\":true,\"nonce\":5,\"roll\":909,\"target\":1998,\"condition_high\":true,\"amount\":1.000000,\"profit\":-1.000000,\"balance\":1000.249200}}", hdl=error reading variable: access outside bounds of object referenced via synthetic pointer, this=0x7fffec000a00) at /home/ebola/Projects/ProvablyFair/libprovablyfair/../../websocketpp/websocketpp/impl/endpoint_impl.hpp:168...

The above happens if I create a std::thread backed pool and call send from threads other then the main thread, if I handle all message processing in my on_message handler...