I didn't have the impression rendering to disk is much of an advantage anyway. And since you can't render areas (why?!?) it is actually quite a disadvantage. It must be a problem deep inside the algorithms of vue. I was able to render huge pictures without any problem and with lightning speed as long as they contain only vue native objects (like plants). I guess the problems only became visible when people were starting to import poser objects with their huge texture maps. And the error seems not even to be reproducible. There is an area of resolution in which vue crashes SOMETIMES (render the same picture, one time it works one time not). I'm afraid e-on is not going to be able to fix this bugs in the next times. I guess you also tried that, but what helps is restarting vue or even the computer before rendering. That clears the memory. But it only helps to get you A LITTLE MORE resources. I guess it is not enough for you.