same issue - same reply - same result - not fixed.
Wonders why if it's a known issue - where is Centova?
Why don't you guys get the fix and put it in an update?
We could call it Centova Cast v3.2.1X ( you can pick the number, it'll be awesome!)
Seriously though - if it's a known issue and there is a known fix- publish it, it's a part of your package we all pay for.
Don't send us on a goose chase to some other company's website and a list of to-do's to fix it - that's your job.
I think the only memory leak is upstairs - get the fix, release an update, issue resolved is what i say. Unless I'm mistaken and I'm paying for something other than a working copy of Centovacast (and included packages).