|
 |
After investigating further, I think the Closing bug may happen when you
click the close button (X) while pov is in the stopping state. Another odd
fact is that POV continues to acquire more memory even though it is
"stopping".
-Nathan
"Nathan Shomber" <nat### [at] rejgond com> wrote in message
news:4278d9ae$1@news.povray.org...
>I have a large scene file that causes a memory leak in the SSE2 version of
>beta3. The first rendering uses up to 300MB of memory which stays
>allocated even when the render is done and I close the output window.
>After the second rendering, pvengin-sse32.exe has 470MB allocated. I am
>rendering using the standard ini file with "+fn +w800 +h600" as my options.
>
> There is also a second issue that POV-Ray does not seem to give up when it
> cannot allocate more memory. When I ran my system out of memory running
> POV-Ray, it just unallocates a chunk of 30MB or so then reallocates it in
> an infinite loop. When I clicked stop, POV-Ray took its time with the
> swap file, but eventually stopped. When I then clicked the close button
> (X in top right), I got the error message posted in beta-test.binaries
> with this subject.
>
>
> I am working on isolating the problematic code. It is a rather simple
> scene with:
> 1) just a couple area lights unioned with media in a difference of
> cylinders
> 2) a LOT of cylinders unioned together with individual pigments made using
> rand
> 3) some boxes.
>
> If there is a known issue with any of these features, I will stop hunting
> for the problem, otherwise, I will trim the scene to the minimum cause.
>
> -Nathan
>
> WinXP Pro SP2
> 1GB (2x512MB) RAM
> Pentium 4M 2.2GHz
>
> PovRay 3.7.0.beta3.icl8-sse2.win32
>
Post a reply to this message
|
|
