Added LOTS of debug output to find SegFault - fixed one possibility where boost does not abort with an error when I cancel but there is still a random SegFault somewhere. Can't find it with logging - maybe it is a bug in the websocket library?! I'll keep on hunting #8. Rebuild Linux x86 binaries. Raspberry Pi and OSX will follow. Changed default Websocket port to 1884 #3