WFS renderer crashes when using the TCP/IP interface

[chohner]

Connecting to SSR in WFS mode reliably crashes with the following error:

libc++abi.dylib: terminating with uncaught exception of type boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::bad_weak_ptr> >: tr1::bad_weak_ptr

Same setup is working fine with the binaural renderer. This usually happens 0-2 seconds after initializing a request. Until the crash, I can see the source moving in the GUI and the scene response over TCP is also sent.

[mgeier]

I've never seen that error, looks like something from deep inside the Boost/ASIO networking library.

It would probably help to get a backtrace from the crash, to be able to locate the exact position in the code where this happens.

[Schroedingers-Cat]

I'm experiencing the same issue using the m4l-SSR-Remote. Though using the latest SSR version, the boost error is gone, what remains however is the bad_weak_ptr. chohner/m4l-SSR-Remote#1
When reducing the update frequency to 1000ms (which produces horrible choppy movements), the SSR instance is likely to crash roughly after an hour. With the update frequency set to 500 or 250, it usually crashes within 10 minutes.