[java-dev] Re: Re: Crash in JitterMatrix.copyMatrixToArray() ?
Joshua Kit Clayton
jkc at musork.com
Wed Feb 6 13:31:13 MST 2008
- Previous message: [java-dev] Re: UdpSender not ready to send
- Next message: [java-dev] Re: Re: Re: Crash in JitterMatrix.copyMatrixToArray() ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
FWIW, upon further investigation, the memory leak only happens if the array is not matched in size to the matrix size (product of all dimensions). So the issue in your example is using one matrixbuf for all inputs where the last input is not the same size as your array and you leak memory. If you disconnect the last input which is a different size than all the others, the memleak disappears (this matrix doesn't get copied to the buffer anyways either if the size doesn't match). I've fixed this for the next version of Jitter (Max 5 only), so for now, if you want to use these whole matrix at a time methods you'll want to make sure that the sizes match or else you'll mem leak. Otherwise use the recommended vector methods which should not be that much slower if at all. Thanks for finding this bug. -Joshua
- Previous message: [java-dev] Re: UdpSender not ready to send
- Next message: [java-dev] Re: Re: Re: Crash in JitterMatrix.copyMatrixToArray() ?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
