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: All of the websocket v120 winrt tests have been disabled right now. They are failing in many of our nightly and rolling builds. They don't seem to be failing with v140 so those are staying enabled.
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: All of the websocket v120 winrt tests have been disabled right now. They are failing in many of our nightly and rolling builds. They don't seem to be failing with v140 so those are staying enabled.