#TSE AXP memory
6 messages in this thread
I'm experiencing heavy memory leakage during rendering when using TSE to create
an AXP object. Any idea what conditions cause this?
— James — Choreo Motion —
>> I'm experiencing heavy memory leakage <<
I knew all those years of hard drugs would finally catch up to you. <g>
> memory leakage . . . years of hard drugs <
Vallium, maybe. <BG> I even got that upgrade, but 360 GB was just too much —
and when I lost the last decoder image I knew I was in trouble. Guess I better
talk to Dr. Allcome!
— Johnny Motion —
James:
I need more information than that, such as a script or script fragment which is
causing the leak. We have not encountered any memory leaks in the AXP module as
of yet.
If you email me some code, I'll be happy to look into it.
Martin
> I need more information than that <
I expected as much. I was hoping there was a simple gotcha I was overlooking
(which may yet be the case). I'll send you an e-mail of the script.
— James — Choreo Motion —
Martin:
Thanks for getting back to me on the TSE AXP memory issue. Just thought I'd
let everybody know the problem was that I didn't use the Puthole command to
clear the gas gauges and it was chewing up memory. Not a TSE memory problem:
A coding oversight on my part.
— James — Choreo Motion —