The memory increase appears to be related directly proportionally to the 
image size (at least for the blank scene).
ie: +w800 +h600 leads to a 9MB increase
+w8000 +h600 leads to a 90MB increase as does +w800 +h6000.

Perhaps a pixel buffer isn't getting flushed after the file is 
saved/displayed/closed?




A slightly Different Issue:

The amount of memory that is allocated and unreturned each render increases 
with the number of objects in the scene.  My sample was rendered with "+w1 
+h1 +fn"

camera{
    location <1,0,0>
    look_at <0,0,0>
}
//i=100000: 3.7 uses 60MB per render 3.6.1a used up to 87MB but dropped to a 
100kB increase.
//i=10000: 3.7 uses 4MB per render 3.6.1a no net increase at all
//i=1000000: 3.7 uses 722MB per render 3.6.1a used 810MB but dropped to 
7.7MB once the render finished.
#local i=100000;
#while (i>0)
    #local i=i-1;
    sphere{
        <i,i,i>,.5
    }
#end


Are the objects not being erased from memory in 3.7?


-Nathan



"Nathan Shomber" <nat### [at] rejgondcom> wrote in message 
news:4278e1de$1@news.povray.org...
> That is according to Task Manager.  (I know, not a reliable source.)  On 
> that same note however, the VM Size increases by 70MB per additional run.
>
> I know that there is a leak because after 3-4 renders, my computer starts 
> using its swap file like crazy and nothing runs or refreshes very quickly, 
> whereas it does during the first few renders.
>
> I have trimmed my code down to a (very) small sample scene that exhibits 
> the problem.  After each rendering pass POV-Ray consumes 10MB more VM 
> space according to Task Manager.  This is compared to 3.6.1a which even 
> after 10 renders only uses a combined total of Mem and VM 10512K + 6224K = 
> 16736K (much less that 3.7 would be (10MB*10=100MB each for both Mem and 
> VM)).
>
> Sample Scene: ( just 2 comments)
>
> //Begin Sample
> //End Sample
>
> -Nathan
>
> "Thorsten Froehlich" <tho### [at] trfde> wrote in message 
> news:4278dc5f$1@news.povray.org...
>> Nathan Shomber wrote:
>>> The first rendering uses up to 300MB of memory which stays allocated 
>>> even when the render is done and I close the output window.
>>
>> How did you determine this?
>>
>> Thorsten
>
>

Post a reply to this message