I'll probably post this in the Massive forum also, but I'm having issues with 3delight rendering an animation.
After 3 frames (there are three passes also) I get the following message:

massive 2.6.16 initialised
Build: Fedora Core release 4 (Stentz)  01:16 06/01/07
*** glibc detected *** renderdl: double free or corruption (!prev): 0xb7e10640 * **
======= Backtrace: =========
/lib/libc.so.6[0xd22424]
/lib/libc.so.6(__libc_free+0x77)[0xd2295f]
/usr/lib/libstdc++.so.5(_ZdlPv+0x23)[0xa85f53]
/usr/lib/libstdc++.so.5(_ZdaPv+0x1f)[0xa85faf]
/usr/local/3delight-6.0.4/Linux-i686/lib/lib3delight.so[0x7a4a13]
/lib/libc.so.6(exit+0xc5)[0xce9c69]
/lib/libc.so.6(__libc_start_main+0xce)[0xcd3dee]
renderdl(wait+0x35)[0x804b461]

======= Memory map: ========
(lots of garbage here)
Received signal 6 (Abort).

[0]     /usr/local/3delight-6.0.4/Linux-i686/lib/lib3delight.so [0x795c19]
[1]     /usr/local/3delight-6.0.4/Linux-i686/lib/lib3delight.so [0x795bad]
[2]     [0x3ba420]
[3]     [0x3ba402]
[4]     gsignal
[5]     abort
[6]     __libc_fatal
[7]     /lib/libc.so.6 [0xd22424]
[8]     __libc_free
[9]     _ZdlPv
[10]    _ZdaPv
[11]    /usr/local/3delight-6.0.4/Linux-i686/lib/lib3delight.so [0x7a4a13]
[12]    exit
[13]    __libc_start_main
[14]    wait

It looks like the renderer is running out of memory - is there anything I can do about this? Is it a Massive issue?

Thanks!