Sent: Saturday, November 01, 2014 4:32 AM
To: softimage@listproc.autodesk.com
Cc: Matt Lind
Subject: Re: Command used within Python Module causes memory leak?
I'm using external Python and am on 2014 SP2 with a QFE.
Yeah not sure here.
Eric T.
On Friday, October 31, 2014 4:29:55 PM, Matt
...@listproc.autodesk.com] On Behalf Of Eric Thivierge
Sent: Saturday, November 01, 2014 4:32 AM
To: softimage@listproc.autodesk.com
Cc: Matt Lind
Subject: Re: Command used within Python Module causes memory leak?
I'm using external Python and am on 2014 SP2 with a QFE.
Yeah not sure here.
Eric T
I'm using external Python and am on 2014 SP2 with a QFE.
Yeah not sure here.
Eric T.
On Friday, October 31, 2014 4:29:55 PM, Matt Lind wrote:
what version of Softimage are you using?
I have been experiencing memory leaks with C++ operators written in
2013 SP1. Same operator compiled for other
what version of Softimage are you using?
I have been experiencing memory leaks with C++ operators written in 2013 SP1.
Same operator compiled for other versions seems to work fine.
I’m tempted to say there is a known issue with memory leaks with Python in past
versions, but I cannot say for su
Just a random suggestion, might work might not:
import gc
gc.collect()
Sent from my iPhone
> On 31-Oct-2014, at 9:10 pm, Eric Thivierge wrote:
>
> Hello again,
>
> Just wondering if anyone has experienced memory leaks when using commands
> within Python modules that have been imported? Doin
Hello again,
Just wondering if anyone has experienced memory leaks when using
commands within Python modules that have been imported? Doing some mesh
merging and attribute transfer within a method of a class I created, and
the memory sky rockets and takes forever. However when I run the same
6 matches
Mail list logo
