Nick Hardeman
Nick Hardeman
I'm actually getting the crash just from making a message: ``` //-------------------------------------------------------------- void ofApp::update(){ if( ofGetFrameNum() == 3 ) { ofxOscMessage m { "/test" }; m.add("something", "else", 20.3f); } }...
When I change to this, then no crash, I am using a nightly from a week or two ago. ``` if( ofGetFrameNum() == 3 ) { ofxOscMessage m; m.setAddress("/test"); m.addStringArg("something");...
I just tried with the test app in #7949 and it hung, and eventually crashed. I am using the latest nightly and macOS 14.2.1. In the Xcode console I see...
Closed by #7949
I don't remember ever receiving the `[warning] ofxOscReceiver: select failed` message. But the crash report is pointing to the same areas in the code we were seeing in practice and...
Hi @artificiel, Thank you for making these tests. When I comment out the INSTANTLY_OUT_OF_SCOPE define, it runs as it should, otherwise it hangs, as you mentioned. I tried it out...
_"do you have the possibility of testing your previously-crashing deployed situation?"_ I don't have a good way to test. It was one of those crashes that took a long time...
Hi @armadillu, Thank you for reporting this. If you make some changes to ofxOscReceiver.h so that it does not start via the constructor and default port, does that avoid the...
This PR will close #8021
When drawing an ofPolyline and a texture is bound, the tex coords get added so that the first point has texcoord.x == 0.0 and the last point has texcoord.x ==...