I did a little test: a simple file, rendered as an animation with 100 frames.
Each frame is the same but when I check the stats the peak memory increases with
each frame. After the first frame the increase is the largest, after that it's
only small steps, but I'm sure this must mean something 8)

Adios!

Remco

Post a reply to this message

Remco de Korte wrote:
> 
> I did a little test: a simple file, rendered as an animation with 100 frames.
> Each frame is the same but when I check the stats the peak memory increases with
> each frame. After the first frame the increase is the largest, after that it's
> only small steps, but I'm sure this must mean something 8)
> 
> Adios!
> 
> Remco

hi remco,

you should be more specific. which pov-ray version do 
you use?

try dumping the heap right before and after each frame
and make some diffs.

(i can send you a hacked mem module which dumps the 
heap contents to a file if the problem really bothers 
you.)

	y.

Post a reply to this message

Tomas Plachetka wrote:
> 
> Remco de Korte wrote:
> >
> > I did a little test: a simple file, rendered as an animation with 100 frames.
> > Each frame is the same but when I check the stats the peak memory increases with
> > each frame. After the first frame the increase is the largest, after that it's
> > only small steps, but I'm sure this must mean something 8)
> >
> > Adios!
> >
> > Remco
> 
> hi remco,
> 
> you should be more specific. which pov-ray version do
> you use?

Windows version 3.1g
> 
> try dumping the heap right before and after each frame
> and make some diffs.
> 
> (i can send you a hacked mem module which dumps the
> heap contents to a file if the problem really bothers
> you.)
> 
>         y.

I'm not trying to compile POV or anything I just noticed this
and thought perhaps it could be of interest for those who have
a clue of what might be going on. Perhaps some more testing
(with an idea in mind of what to look for) could help. 

Regards,

Remco

Post a reply to this message

<snip>

> > you should be more specific. which pov-ray version do
> > you use?
> 
> Windows version 3.1g

i have never noticed a memory leakage with 3.02 on various
unix (and similar) systems.

> > try dumping the heap right before and after each frame
> > and make some diffs.
> >
> > (i can send you a hacked mem module which dumps the
> > heap contents to a file if the problem really bothers
> > you.)
> 
> I'm not trying to compile POV or anything I just noticed this
> and thought perhaps it could be of interest for those who have
> a clue of what might be going on. Perhaps some more testing
> (with an idea in mind of what to look for) could help.

i also have no time for inspecting the problem,
i can only offer the heap dumping function to
someone who is willing to do the compiling and
diffing. there are perhaps other people having
the same problem, let's wait what they say.
till then, save the source of your animation, 
.ini files etc and forget it.

	y.

Post a reply to this message

Tomas Plachetka wrote:
> 
> <snip>
> 
> > > you should be more specific. which pov-ray version do
> > > you use?
> >
> > Windows version 3.1g
> 
> i have never noticed a memory leakage with 3.02 on various
> unix (and similar) systems.
> 
> > > try dumping the heap right before and after each frame
> > > and make some diffs.
> > >
> > > (i can send you a hacked mem module which dumps the
> > > heap contents to a file if the problem really bothers
> > > you.)
> >
> > I'm not trying to compile POV or anything I just noticed this
> > and thought perhaps it could be of interest for those who have
> > a clue of what might be going on. Perhaps some more testing
> > (with an idea in mind of what to look for) could help.
> 
> i also have no time for inspecting the problem,
> i can only offer the heap dumping function to
> someone who is willing to do the compiling and
> diffing. there are perhaps other people having
> the same problem, let's wait what they say.
> till then, save the source of your animation,
> .ini files etc and forget it.
> 
>         y.

  It is a documented phenomenom and there is a logical reason for it. I
just don't remember off hand what it is.

-- 
Ken Tyler

See my 1000+ Povray and 3D Rendering and Raytracing Links at:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Tomas Plachetka wrote:
> 
> <snip>
> 
> > > you should be more specific. which pov-ray version do
> > > you use?
> >
> > Windows version 3.1g
> 
> i have never noticed a memory leakage with 3.02 on various
> unix (and similar) systems.
> 
> > > try dumping the heap right before and after each frame
> > > and make some diffs.
> > >
> > > (i can send you a hacked mem module which dumps the
> > > heap contents to a file if the problem really bothers
> > > you.)
> >
> > I'm not trying to compile POV or anything I just noticed this
> > and thought perhaps it could be of interest for those who have
> > a clue of what might be going on. Perhaps some more testing
> > (with an idea in mind of what to look for) could help.
> 
> i also have no time for inspecting the problem,
> i can only offer the heap dumping function to
> someone who is willing to do the compiling and
> diffing. there are perhaps other people having
> the same problem, let's wait what they say.
> till then, save the source of your animation,
> .ini files etc and forget it.
> 
>         y.

This was not really a problem for me, I just noticed it. I think the source I
used for this is not really relevant (it isn't really relevant in general ;)).
Thanks for your help. 

Regards,

Remco

Post a reply to this message