 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I've been tracing lots of animations lately, and after
some time my computer starts stuttering, WINAMP
freaks out, my internet-connection zaps out...
I'm wondering if this has got anything to do with
the reported bug of POV 3.5s memory-handling,
and want to do some checks.
Anyone know a good, easy to use freeware programm for
Win98, so that I can check memory usage?
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmx de
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3CF4FB72.D0F9731D@gmx.de> , Tim Nikias <tim### [at] gmxde> wrote:
> I'm wondering if this has got anything to do with
> the reported bug of POV 3.5s memory-handling,
Which bug??? I am not aware of any such bug report and I am sure there isn't
any problem with the memory handling either ... so what is the purpose of your
message?
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Try Start -> Programs -> Accessories -> System Tools -> System Monitor, and
add the charts you want. It's a pretty powerful tool.
- Kevin R.
"Tim Nikias" <tim### [at] gmxde> wrote in message
news:3CF4FB72.D0F9731D@gmx.de...
> I've been tracing lots of animations lately, and after
> some time my computer starts stuttering, WINAMP
> freaks out, my internet-connection zaps out...
>
> I'm wondering if this has got anything to do with
> the reported bug of POV 3.5s memory-handling,
> and want to do some checks.
>
> Anyone know a good, easy to use freeware programm for
> Win98, so that I can check memory usage?
>
> --
> Tim Nikias
> Homepage: http://www.digitaltwilight.de/no_lights/index.html
> Email: Tim### [at] gmxde
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
No offense!
I read several reports stating that memory usage
increased during animations/interrupted renders,
as if POV-Ray wasn't making all memory available
again after the termination of a render.
I'm not sure of the status of those reports, if
they were confirmed officially, or if something
else might be causing the memory increase.
I just noticed that when POV-Ray is tracing
several scene as animations, my computer at
some point gets sloppy and sometimes finally
crashes.
The purpose is to get some means to actually
check what is going on. Please note that
this post was put in "general", not
"beta-test" and was asking for freeware
programs to monitor memory usage.
I'm aware that you are actually a little "afraid"
of rumours, so I'll be less POV-offensive
the next time, okay? ;)
Thorsten Froehlich wrote:
> In article <3CF4FB72.D0F9731D@gmx.de> , Tim Nikias <tim### [at] gmxde> wrote:
>
> > I'm wondering if this has got anything to do with
> > the reported bug of POV 3.5s memory-handling,
>
> Which bug??? I am not aware of any such bug report and I am sure there isn't
> any problem with the memory handling either ... so what is the purpose of your
> message?
>
> Thorsten
>
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3CF540FE.6B43B2F5@gmx.de> , Tim Nikias <tim### [at] gmxde> wrote:
> I'm not sure of the status of those reports, if
> they were confirmed officially, or if something
> else might be causing the memory increase.
Those have been explained a very long time ago in p-beta-test: Some people
observed memory use increasing by a few KB with each render using the system
monitor, which is exactly the size needed to store the statistics and other
message output. So there is no problem and never was.
I should point out that the system monitor just like any other external tools
are completely unsuitable to measure any memory usage in a correct manner.
There is no way to get the correct information without access to the source
code and linking it with libraries suitable for that task or enabling the
POV-Ray internal memory tracking. All other measurements gained with external
methods could just be replaced by random data which would say as "much"!
> I'm aware that you are actually a little "afraid"
> of rumors, so I'll be less POV-offensive
> the next time, okay? ;)
Well, you already responded to a rumor so I suppose you now know why they are
a problem :-) Even if they were explained long ago as being false and
baseless someone will have missed that explanation...
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> Well, you already responded to a rumor so I suppose you now know why they are
> a problem :-) Even if they were explained long ago as being false and
> baseless someone will have missed that explanation...
>
Yeah, like me... ;)
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3cf612bb$1@news.povray.org> , "Gilles Tran" <tra### [at] inapginrafr>
wrote:
>>So there is no problem and never was.
>
> Memory problems that became apparent in animations have been reported before
> :
>
> Change 1512 on 2002/04/14 by chrisc@lilliput
> Fix pigment_pattern memory leak reported in
> http://news.povray.org/3cb3217f$1@news.povray.org
>
> Change 1300 on 2001/12/30 by thorsten@host27
> Should fix the JPEG image reading memory leak
> http://news.povray.org/3be2ef0d@news.povray.org
> (note: this one was fixed, apparently...)
These are not those reports I have been referring to or which this thread is
about. There was a long thread in p.beta-test (I don't feel like searching
for it now) that was about someone insisting there was a problem while there
was not.
> A last one was reported recently but not confirmed.
> http://news.povray.org/3CDFFDB3.F24905A9@gmx.de
As explained, looking at the system monitor is absolutely unsuitable to check
memory usage...
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>
> [...]
>
> > A last one was reported recently but not confirmed.
> > http://news.povray.org/3CDFFDB3.F24905A9@gmx.de
>
> As explained, looking at the system monitor is absolutely unsuitable to check
> memory usage...
>
I have not been able to supply a test scene for this until now so no need
to have much fuzz about it, but if the harddisk starts trashing after 250
frames despite 256 Mb RAM this IMO is a suitable indication for memory
consumption.
Christoph
--
POV-Ray tutorials, IsoWood include,
TransSkin and more: http://www.tu-bs.de/~y0013390/
Last updated 05 May. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3CF622D4.238E3ABA@gmx.de> , Christoph Hormann
<chr### [at] gmxde> wrote:
>> As explained, looking at the system monitor is absolutely unsuitable to check
>> memory usage...
>>
>
> I have not been able to supply a test scene for this until now so no need
> to have much fuzz about it, but if the harddisk starts trashing after 250
> frames despite 256 Mb RAM this IMO is a suitable indication for memory
> consumption.
Well, how many messages are in the message window by then? I suppose many.
And they are likely all over the application memory space which suggests a lot
of memory fragmentation. Consequently after each frame there can a little
memory that is no use as it is a leftover fragment when rendering the next
frame which uses a similar memory allocation pattern.
The effect many not be as visible when rendering different scenes, but it is
simply in the nature of memory allocation. Just like your harddisk memory
gets fragmented, and even worse, with memory there is no way to "defragment"
it other than freeing all memory allocated, which is essentially restarting
the program ... essentially you are chasing ghosts here.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Well, how many messages are in the message window by then? I suppose many.
> ...
This note got me thinking. Is there a way to have POV-Ray
(in Windows) flush the message-stream? Perhaps that's whats
causing the most trouble for Windows users...
And I mean something different than restarting POV manually.
Something automatic would be helpful, I guess...
Suggestions?
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
