ofxOscReceiver::getNextMessage with pointer

[kimon-satan]

I'm not sure why but when I use a pointer rather than an object to get the next message I get a CPU spike. I'm on commit 7bf5c5e

this is my code which I note is the same as the example in ofBook

//in update
while (receiver.hasWaitingMessages()) {
ofxOscMessage m;
if(receiver.getNextMessage(&m)){ /do blah/}
}