"Tony[B]" wrote:

> ...when a render doesn't finish after 1 day, 7 hours, 29 minutes and 1
> second, reporting that there was a "Rendering error. Out of memory. Cannot
> allocate 144 bytes for octree block." Yup, that hurts a lot. Especially when
> you've tried to leave the machine alone, so it renders faster during this
> time period. Can someone tell me why this happened? What is an octree block,
> and why did it eat up all my RAM?
>

Ahh, just happened to me on a 800*600 radiosity image, and I did raise the swap
up to 450 Mb... But I could resume the render without any problem (it had the +C
switch). At least it didn't crash Windows, like post-process does when out of
memory.
I wonder what's going to happen when I'll render the same picture at 16 times
the current size, though. Perhaps I'll render it chunk by chunk.
G.

Post a reply to this message