Am 26.11.2013 18:31, schrieb clipka:
> Am 26.11.2013 18:16, schrieb James Holsenback:
>>>
>>> Still doesn't make much sense to me. Mind e-mailing the complete scene +
>>> all render settings? (See the dev newsgroup for my e-mail address).
>>>
>>
>> a little bit too big to email ~15MB, so I put it on my wiki testbed ...
>> see your email for the link
>
> Thanks, but I guess I've nailed down the culprit already - after
> accidently getting my Windows system into swap hell by "nothing more"
> than cranking up the AA mode 3 quality settings (something like +am3
> +ac0.999 +a0.001 +r9). The quality settings shouldn't have any effect on
> the memory consumption during AA mode 3, but obviously they do.
>
> That was the clue I needed. Turned out to be a stupid bug, actually.

BTW, the render abort you experience is probably due to an excessively 
large chunk of memory being passed from one of the render threads to the 
front end.

Post a reply to this message