When the OSC server receives an OSC message with two consecutive string arguments and the first string argument is of a positive length divisible by four, the next string argument will be read as an empty string, and other future arguments may also be corrupted.
I have a fix. Will submit a pull request.