We also noticed a memory leak just by using a very basic mel loop with a
setAttr, under maya7.0.1 linux.
Open a fresh maya, and type this in script editor, to see if you notice it
too?
for ($i=0; $i<100000; $i++)
{
setAttr persp.tx 0;
}Nicolas On Fri, Oct 24, 2008 at 10:25 AM, bruno ebe <[email protected]> wrote: > > Hi again > > ok I tried the MEL command in the same loop (but in MEL) over the same > fluid container and had no leak > (I even tried it several times to be sure that the leak was not just > smaller...) > > so I tried to use the mel.eval() command from python inside my python > loop > > for x in range( resX ): > for y in range( resY ): > for z in range( resZ ): > mel.eval( `fluidVoxelInfo -voxelCenter -xi ` > +str(x)+` -yi `+str(y)+` -zi `+str(z)+` `+fluidName+`;`) > > but this way I have leaks again... > can it be that the python version of fluidVoxelInfo is in fact equal > to: mel.eval('fluidVoxelInfo...) ? > > regards > Bruno > > > > On Oct 24, 10:30 am, bruno ebe <[email protected]> wrote: > > Hi Chris > > I am using maya 8.5 on windows 64bits > > any known issues with that? > > > > I am about to try the same code in MEL and keep you posted > > regards > > Bruno > > > > On Oct 24, 1:11 am, "Chris G" <[email protected]> wrote: > > > > > What version of Maya are you using? > > > > > On Thu, Oct 23, 2008 at 11:30 AM, bruno ebe <[email protected]> > 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 > > > --~--~---------~--~----~------------~-------~--~----~ Yours, Maya-Python Club Team. -~----------~----~----~----~------~----~------~--~---
