Have you tried running your code against the latest Processing build from GitHub? Because the leak issue has been fixed.
If it's the same issue, your code should run without problems.
If it's a different issue, then you should recreate your problem in a small runnable example.
File an issue if it turns out that 1) it's a bug not a coding error and 2) it persists in the latest build.
If it's the same issue, your code should run without problems.
If it's a different issue, then you should recreate your problem in a small runnable example.
File an issue if it turns out that 1) it's a bug not a coding error and 2) it persists in the latest build.