Wetterberg

I'm having a problem with memory usage rising dramatically. I've traced it back to regexp, which I use to chop up OSC

causes memory use to climb slowly, but steadily, on 6.1.8.

What do? Are there alternative ways of doing this? I'd rather not end up with osc-route and the like, since this is such an easy vanilla solution, but I can't have the OSC itself bring my rig to its knees...

causes memory use to climb slowly, but steadily, on 6.1.8. 

What do? Are there alternative ways of doing this? I'd rather not end up with osc-route and the like, since this is such an easy vanilla solution, but I can't have the OSC itself bring my rig to its knees...


regexp-problem-memory-leak

Do you mean that osc-route is very CPU-hungry ?

Could also be done without regexp, may be even more efficient.

^crap, i forgot about 'atoi'/'itoa'. nice one. that's the solution you want!

Both solutions are great, unfortunately the atoi only chops off the first /, not subsequent ones. Raja, I've confirmed yours doesn't leak either! YOU'RE THE WINNER! YAY! :)

@stephane: No, I just have a dogma of not using externals. It makes my patches much more portable.

No doubt RAJA provided the most elegant solution. But for the sake of completeness I should mention that the atoi method also works for multiple '/' and seems a bit faster (about 20%).

Just wanted to jump in to confirm the memory leak on OS X 1.9.4 /Max 6.1.8

@WETTERBERG: Did you file a bug report? I think this is something that should be fixed as it potentially crashes Max ...

Just wanted to jump in to confirm the memory leak on OS X 1.9.4 /Max 6.1.8
@WETTERBERG: Did you file a bug report? I think this is something that should be fixed as it potentially crashes Max ...


I know that this may be a bit off-topic, but I wanted to mention that CNMAT offers a (relatively) new set of externals to manipulate and format OSC data natively in max, called "o." (odot). We will be offering our first official release soon, but for now, you can download an alpha version to wet your appetite. You may see a huge increase in speed when it comes to parsing, formatting, and doing math on what we call odot bundles, which offer an aggregate data type in Max.

Hope this helps. If you're interested in going further or getting more details on usage, please ping me directly.

I know that this may be a bit off-topic, but I wanted to mention that CNMAT offers a (relatively) new set of externals to manipulate and format OSC data natively in max, called "o." (odot).  We will be offering our first official release soon, but for now, you can download an alpha version to wet your appetite.  You may see a huge increase in speed when it comes to parsing, formatting, and doing math on what we call odot bundles, which offer an aggregate data type in Max.

Hope this helps.  If you're interested in going further or getting more details on usage, please ping me directly.
jml / Jeff Lubow
CNMAT


No doubt RAJA provided the most elegant solution

no no! i think overall, Broc's solution with atoi is the best and always was(it's as simple as learning the ascii code for "/"...).

Regexp problem - memory leak?