Open jvcleave opened 10 years ago
I can confirm the poco exception on Linux. @arturoc do you know what's going on?
it's probably related with the destruction order, i don't think it's a good idea to not remove the listener though, if the object is destroyed while the app is running it'll crash when the event is triggered again
A workaround that is working for me (also works in the examples) is to use a pointer forofxOscParameterSync
If the examples in question are "addons/oscSenderExample" and "addons/oscReceiveExample", then I can not replicate this bug on Debian (64bit) as of b5db2ccc97bbe7406ca5fa1feaff4f3cfdf2012b. @bilderbuchi can you confirm this?
Those are not the correct examples, the correct ones are in https://github.com/openframeworks/openFrameworks/tree/master/examples/gui with the names as in the OP.
@jvcleave can you confirm this error in the latest master?
Mac 10.8, Xcode 5.01
Running the oscParametersSender or oscParametersReceiver example and exiting the app causes an Poco exception in ~ofxOscParameterSync when it goes to remove the listener
removing the ofRemoveListener... allows the app to exit cleanly
backtrace