[java-dev] Re: Re: Crash in JitterMatrix.copyMatrixToArray() ?

On Feb 7, 2008, at 12:37 PM, vboehm at gmx.ch wrote:
>
> hmm, interesting. i didn't know about copyArrayToMatrix() - must  
> have slipped in unnoticed somewhere inbetween.
> i was using copyArrayToVector() before and it works fine, as you said.
> on a speed comparison however, i was happy to notice that  
> copyArrayToMatrix() is much faster than the vector method - at  
> least in my situation. cpu usage came down half way for a 100x100  
> matrix (measured with top).
>
> BUT, i can't escape the memory leak even if the array and the  
> matrix match in size!
> in the simplified example below, memory is still leaking. where am  
> i going wrong?
> any help is welcome, since the speed increase could be crucial to  
> the project i am working on.

Sorry, copyArrayToMatrix() *always* leaks in Jitter 1.6.x. It is  
copyMatrixToArray() which has no memory leak if matched in size.  
These methods were added later in the development cycle and were  
obviously not carefully tested w/r/t memory leaks. Solution for both  
in the next version for Max 5 only, but that doesn't really help much  
for now. Sorry about that.

The one thing you might be able to hack together now is the creative  
use of one large array being sent into a single row matrix to  
jit.scanwrap to wrap that long row into a 2d matrix.

-Joshua