"Roman" <nomail@nomail> wrote:
> As SharkD mentioned, the error also occurs in the 32bit version:
>
http://news.povray.org/povray.beta-test/message/%3Cweb.4957638b86257958d2ca984a0%40news.povray.org%3E/#%3Cweb.4957638
b8
> 6257958d2ca984a0%40news.povray.org%3E

Not seen here yet. (Not when leaving the system alone while it's rendering, at
least; I've seen some errors regarding file access stuff, but usually I was
loading something else in the editor at that very same moment.)

> > At the moment I suspect that it's actually all about timing,

> But then why does it work with a radiosity count of less than ~300?

Maybe because it just changes the timing.

> To me, from
> an outside point of view, it seems more likely that there is some memory
> problem with the radiosity feature (or somewhere else).

How much RAM do you have available? I'm running on 2 GB here, and don't see any
such problems, although I'm running other stuff in parallel, like MS Visual
Studio and the like.

> It looks as if some
> allocated memory wasn't freed properly, causing trouble when POV-Ray wants to
> go on with the next scene file, or that an array overflew. Also the memory dump
> error popup (saying: unhandled exception) in the end of rendering a single scene
> gives rise to such an assumption.

"Unhandled exception" could be just about anything.

Could also be related to thread synchronization. Maybe some cleanup stuff not
fully multithread-safe, and two threads trying to clean up at the same moment.

Unfortunately it's very hard to pin down such issues unless they can be
reproduced on a system with a debugger running.

Post a reply to this message