#3 Screen corruption on large render

open-accepted
nobody
None
5
2009-11-13
2009-11-08
No

Using v0.75 and a GeForce 8600GT 256MB (with nvlddmkm 8.15.11.9038, ForceWare 190.38, Win7 64):

Trying to render a flame at 10240x5760 results in an out of memory error message while the program continues running. Graphics corruption occurs with dots (about 4x4 pixels, I think) being sprinkled all over the screen. Dots remain after flam4 has been closed, and can only be removed by rebooting.

Discussion

  • Keldor

    Keldor - 2009-11-13
    • status: open --> open-accepted
     
  • Keldor

    Keldor - 2009-11-13

    10240x5760 is vastly larger than can fit in your GPU's memory. I'm not sure why it's not terminating the render when it gets the out of memory error, however... That corruption is typical of what "should" happen after a failed buffer allocation and then urnning the kernal anyway - it's literally rendering over whatever is in your graphics memory, such as the screen buffer. The problem is that it shouldn't run the kernal when it fails to allocate enough memory! I'll look into it.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks