This is something going on with websocketpp and I'm not sure if actually in the client or in the test server. The test has been disabled for now.
Starting test case close_tests:close_callback_client_websocket...
test_runner(83432,0x1040ad000) malloc: *** error for object 0x1040aac70: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6
Update - doesn't seem to be specific to OS X, it happens on Windows as well.
Comments: Also disabled the following test which was failing on v120 winrt: send_after_close_callback_client
Starting test case close_tests:close_callback_client_websocket...
test_runner(83432,0x1040ad000) malloc: *** error for object 0x1040aac70: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6
Update - doesn't seem to be specific to OS X, it happens on Windows as well.
Comments: Also disabled the following test which was failing on v120 winrt: send_after_close_callback_client