Am 12.04.2011 02:41, schrieb Tor Olav Kristensen:
>
> I get this error message:
> "Parse Error: bad allocation  Render failed"
> - after the code below has been running for about 3 seconds.
>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7
>
> #version 3.7;
>
> #while (true)
>    #local Fn = function { transform { translate<0, 0, 0>  } }
>    #undef Fn
> #end // while
>
> // ===== 1 ======= 2 ======= 3 ======= 4 ======= 5 ======= 6 ======= 7

Having had a closer look at the code, I can confirm that this problem 
indeed depends on the amount of memory installed in, and/or addressable 
by, the user's computer.

As of now, POV-Ray "only" allows a maximum of 1048575 functions per 
scene. Unfortunately, this is also the number of entries in a certain 
table of function-related data POV-Ray allows before it re-uses entries 
marked as deleted.

While this is good for parse speed in scenes using a lot of functions 
(POV-Ray doesn't have to waste time searching the table for undef'd 
entries), it's fatal for scenes re-defining functions over and over again.

Post a reply to this message