[jitter] Re: Homing in on the problem

Hi Tom

It sounds like i'm doing a similar things to you - with some similar problems that i suspect are down to memory leaks somewhere (but i think i've ruled out my own Java bugs now! ha ha ha! :)

One issue i came up against a while ago (a runaway memory leak) was a similar thing to yours - my solution (/hack) was:

Make the var you assign your matrix to a member variable (your "jm" is my "jitterMatrix") and each time you reset it do "freePeer()" - like this:

if (jitterMatrix != null) {
  jitterMatrix.freePeer();
  jitterMatrix = null;
}

Hope that helps.

My problem is that when loading images (into jit.qt.movie objects via an asyncread, then applying a soft edge filter with jit.gl.slab, then piping that into a jit.gl.videoplane to wave it about and then sending it to render) that every now and again (one in 50?) times the thing appears just white with no error message or excuse or anything.

I am using the incremental Jitter framework update (jitterapi_x2_121207.dmg) so i guess i should replace the asyncreads with just "read" (and go back to 1.6.3) and see if that solves it. However, that looks rubbish as it interrupts the stuff already on screen.

Ring any bells, anyone?

(again, this is a huge load of patches so hard to post an example and, in theory, it has already launched yesterday!)

yours

jonny B