Forums > Jitter memory leak > eventual crash

September 3, 2013 | 3:14 pm


I’m experiencing what appears to be a memory leak in The attached illustrative test patch is a simple mod/combo of the and help files, with the resolution boosted to the 1920 x 1920 I’m running. Mac Activity Monitor shows decreasing free memory and increasing VM size before eventually stabalizing at less desirable stats.

This test patch doesn’t actually crash, but my actual patch (too complex to send) does sometimes when I have a lot more going on. (Per another thread, I’ve tried modifying (max.jvm.option -Xms256m and max.jvm.option -Xmx1024m), which has resulted in fewer crashes and longer runs before crashes.) Some of the potentially relevant other differences between the attached simple test patch and my actual (crashing) patch are 1) separate standalones for the send and receive sides of things on one machine via localhost, 2) bitmap images rather than generated noise, 3) net.tcp.send/recv are simultaneously using Java to communicate control data between standalones but on a different port than

System: Mac 2.66Ghz quad core, 8GB RAM, OS 10.6.8, 64-bit mode

BTW, I’ll eventually need to port this to Windows as well.

Any insights appreciated. Thanks!


September 5, 2014 | 9:06 am

Was this ever investigated more closely? I’m seeing the same thing on as well. Physical memory used by Max increases for each image sent (single frame, 1920 x 1080). Eventually it crashes.

I’ll put together a patch that shows this, but was curious if others saw this as well.


September 5, 2014 | 11:13 am

And here’s a patch showing the leak. Mac 10.9.4, Max 6.1.7. Matrix sent to PC running windows 7, max 6.1.7.

– Pasted Max Patch, click to expand. –

September 5, 2014 | 11:31 am

and a little more info:

seems that the memory keeps growing till it gets to ~500mb, on BOTH & Once it hits this threshold it’s steady. Recreate the object and it releases the memory and the process starts over. Is there a buffer setting on these objects? I would hope that once the image made it to its destination it would be removed from the buffer (if this is what is going on).

Any thoughts on this? I’m still having to work in 32-bit land with a pretty big app, so losing 500mb of memory to this isn’t really ideal.


Viewing 4 posts - 1 through 4 (of 4 total)