"Tom York" <alp### [at] zubenelgenubi34spcom> wrote:
> CShake <cshake+pov### [at] gmailcom> wrote:
> > I've been getting 'Fatal error in renderer: Out of Memory' recently in a
> > few of my scenes (in 3.7b31, both in Windows and Linux)
>
> As you've found, it's seemingly triggered by the large number of lights traced
> through media in the scene, not media properties directly.
>
> It looks like one of the calls to std::sort in
> MediaFunction::ComputeMediaLightInterval is causing a bad_alloc exception to be
> thrown, probably due to the use of a fixed number of elements (64) for
> LightSourceEntryVector and friends. I haven't spent much time on this but there
> are lots of FIXME comments associated with this fixed size so presumably this is
> a known (or anticipated) issue.
>
> Doubling the fixed array size universally allows the scene to render, until the
> number of lights in the array is doubled in the scene file which brings back
> the problem again.
>
> Tom

Was this ever fixed/corrected/worked around/something-or-other in b32?

I have a scene with a single (area-)light, no media but a whole bunch of objects
(~2500) which renders fine until I make them transparent - at which point I get
that same "out of memory error".

Which I searched on and found this thread...

(By ~2000 or so pretty much every computer in the known universe understood how
to use virtual memory and I thought messages like "out of memory" were an
archaic artifact of the bad old days. In a sense this error message is making
me feel young again... ;-)

Post a reply to this message