Hi,
As a guess I would look into the source of
fluidVoxelInfo
As it is where the work is actually done.
For instance I'd expect this to leak too, though no variable is even
using the result :
for x in range( resX ):
for y in range( resY ):
for z in range( resZ ):
fluidVoxelInfo( fluidName, voxelCenter=True, xi=x,
yi=y, zi=z)
And it's most probably the command fluidVoxelInfo that is leaking, and
not Python related
Olivier
bruno ebe wrote:
> Hello everybody
>
> I am trying to develop a scripted plugin in python
> In this plugin I go through all the voxels to get their position
>
> for x in range( resX ):
> for y in range( resY ):
> for z in range( resZ ):
> voxPos=fluidVoxelInfo( fluidName, voxelCenter=True,
> xi=x, yi=y,
> zi=z)
> ...
>
> When running this plugin I can see the memory increasing but it never
> flushes
> I started debugging by commenting out everything and I then figured
> out that the problem was in the loop
> and in this loop was left only this line:
> voxPos=fluidVoxelInfo( self.__fluid__, voxelCenter=True, xi=x, yi=y,
> zi=z)
>
> my idea is that the variable voxPos is not reused and some new part of
> the memory is allocated...
> I thought that python managed memory and variables by itself
> so I am not really sure of what I am stating there...
>
> does anyone already got this kind of issue? or smells where it can
> come from?
> maybe there is a python command to force a variable to flush? this can
> be an interesting test but I dont know such command
>
> thanks a lot for your help
> best regards
> Bruno
>
> >
>
>
--
Olivier Renouard
--~--~---------~--~----~------------~-------~--~----~
Yours,
Maya-Python Club Team.
-~----------~----~----~----~------~----~------~--~---
