Looks like a tremendous scene! I think you're on the right track for getting it to render, if it is indeed possible with the amount of memory-using elements you have in the scene.
As far as these crashes being new to 2.0.2.1 or other recent versions, to my knowledge we've yet to see true side-by-side comparisons with older versions. If anyone wants to do this with their more demanding scenes and *verify* that it's actually a new problem, that would be tremendously helpful. From what I can see it just seems like people are trying more and more complex scenes (which is a natural progression) and it happens to have coincided with the final release, so it *appears* to be related to newer releases, but I am not convinced that it actually is. I saw plenty of instances of the memory-related errors prior to the final release, and it's just something we'll have to put up with until we are able to go 64 bit and/or implement better error handling (in which case the problem would still fundamentally exist, it would just be handled more gracefully).
In any case we are investigating these issues on our end already, but some conclusive side-by-side testing from the user community would definitely help.
One thing I will say is that there were some GI-related optimizations made specifically in the last release, 2.0.3.1. Are you using the latest version?
- Oshyan