openframeworks / openframeworks/openFrameworks
ofxOscReceiver::getNextMessage with pointer
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
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 7bf5c5eeb29fcf3
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/}
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start at ofxOscReceiver::getNextMessage and compare the pointer-based call described in the title with the update-loop example; reproduce the CPU spike on commit 7bf5c5eeb29fcf3. Done means identifying the cause and verifying that receiving messages no longer causes the spike.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100