Closed notnot closed 1 year ago
I figured out that the >100% load issue only appears when i have a serial device file open, which is weird i think. Even if nothing is read from or written to this file, the recent go runtime seems to spend a lot of time on it, when osc conn.Serve() is also running. I don't yet have an idea how to proceed debugging this, but i think package osc isn't to blame. I believe i found a flaw in the go runtime...
Closing this as it sounds like it isn't an issue anymore
I have noticed that an application that i am developing which uses package osc has > 100% CPU load even when no OSC messages come in, when i build my executable with go1.9 and go1.10 on OS X 10.10 and 10.12. When i build with go1.7 and 1.8 the CPU load is just a few %, as expected. My application uses GLFW and OpenGL, it is fairly small and simple still, but it depends on some external hardware. I could try and make a more minimal application that doesn't have these dependencies and send you the source.