Well, I restarted my computer, and that fixed it for now. I think if
it's memory then it's part of another potential bug in PovWin 3.1 that
Lutz already reported.

I have 256 meg of RAM and the scene just isn't big at all. My system has
been frequently getting semi-paralyzed when using Moray and the new
PovWin.  Everything's fine for a while, and then Povray won't start.  I
go into task manager and there is "Povray (Not Responding)" needing to
be shut down.  After that Moray always becomes super slow with every
action delayed by 10 seconds or so. (I have a peppy 400mhz PII) and I am
lucky to be able to save and close. Sometimes restarting Moray seems to
clean everything up. Other times, I have to restart.

If this problem is tying up my memory, then maybe it is also causing the
StretchIDBits problem as well.

Lutz said he was waiting for the PovWin Source to take a look.

povray.org admin team wrote:
> 
> >I can't be sure, but I think I rendered images this big with earlier
> >versions of POV-ray and I never encountered this error.
> 
> This happens when you have a scene that maxes out your memory, AND you try to
> display a large image. The windows API function call that we use to draw to the
> render window (called StretchDIBits) fails in an unusual manner (it doesn't
> return an error code, but indicates that it copied a total of 0 lines).
> 
> As far as we can tell there's no workaround, so we display the message you see.

Post a reply to this message