Stefan, It sounds like you're watching the "Mem Usage" column of the task manager. This can be deceptive as it really only reflects the RAM usage and leaked memory tends to migrate to the disk pages through disuse. I haven't looked at this in SR3 (as opposed to SR2.1) before today, but it does look like the leak still exists. Here's a method of reproducing it: 1. Bring up the task manager, select "View::Select Columns::VM Size". 2. Launch Poser 5 SR3 into factory default state (i.e. 3 default lights and casual Don with hair). 3. Select Light 1 and set the shadow map size to 1024* 4. Select render settings and set to "Production Mode* 5. Note the value of the "VM Size" for the Poser process in the task manager. 6. Render a movie using "Current Render Settings" across the default 30 frame range of the static scene (i.e with no animation). About 10 minutes. 7. After the end of the rendering note the "VM Size" of the Poser process. It will have risen by about 120-150 MB. Minimising the Poser window will free up RAM ("Mem Usage") but won't effect the leaked memory in VM. *The best I can tell is that the memory leak is associated with shadow mapping, hence the setting of production mode which enables this. The actual setting have been somewhat difficult to pin down, it could be that there are in fact several sources of leaks. Bill