too high a resolution for cuda causes video corruption

Bug #495986 reported by foundation
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fractal Fr0st
New
High
Unassigned

Bug Description

When you choose to render above a certain threshold (not sure what it is, perhaps amount of video memory that you have?) you get a out of memory cuda error (not the bug) but after that if you click ok and let it continue on, I get random pixels sprayed around the screen. I am using a quadro fx 3700m with 1GB and it does this when rendering 4000x3000 or 5000x3500. This also happens with flam4 standalone program (same dialog, pixel corruption etc.). A restart is required to get the pixels to go away.

If there is indeed a hard limit for flam4 based on the video card's memory, it'd be nice if it checked that before starting the render, and regardless it should probably force quit the rendering rather letting it proceed and corrupt video memory.

Changed in fr0st:
importance: Undecided → High
Revision history for this message
foundation (brynf) wrote :

with 1.1, just tried rendering a batch of images with 2000mb of memory required, and it caused corruption, then it blue screened, which I haven't previously seen. Though I have a different video driver, cuda version etc. so it's like a problem with the driver handling the error condition badly. Hopefully opencl version will have better error handling to report back to frost

Revision history for this message
rockachu2 (rockachu2) wrote :

How are you rendering @ that size? My comp won't let me go above 2250px wide!

Revision history for this message
foundation (brynf) wrote :

I'm using video cards with 1 or 2GB of video memory. When you say your computer won't let you go above 2250, do you mean it crashes above that, or the software won't let you enter anything above that?

Revision history for this message
foundation (brynf) wrote :

Perhaps one idea to amerliorate this issue, would be to allow the user to enter in the preferences how much video memory they have, and then pop up an error box if the pixel dimensions are more than some percentage of that memory. With my 2GB card I've been able to render 1.5GB images. We could do some experimentation on what approximage percentage is that works fairly universally.

Revision history for this message
Andrew Ostrovsky (moipokupki) wrote : Re: [Bug 495986] Re: too high a resolution for cuda causes video corruption

Most of the rendering that I do is 3600 by 2700 and Fr0st, flam3, flam4,
Apophysis, Apophysis-7x
don't seem to have problem with it, yet when I go twice as high flam4 engine
will not work.

On Sat, Jan 22, 2011 at 11:17 AM, foundation <email address hidden>wrote:

> I'm using video cards with 1 or 2GB of video memory. When you say your
> computer won't let you go above 2250, do you mean it crashes above that,
> or the software won't let you enter anything above that?
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (651132).
> https://bugs.launchpad.net/bugs/495986
>
> Title:
> too high a resolution for cuda causes video corruption
>
> Status in Fractal Fr0st:
> New
>
> Bug description:
> When you choose to render above a certain threshold (not sure what it
> is, perhaps amount of video memory that you have?) you get a out of
> memory cuda error (not the bug) but after that if you click ok and let
> it continue on, I get random pixels sprayed around the screen. I am
> using a quadro fx 3700m with 1GB and it does this when rendering
> 4000x3000 or 5000x3500. This also happens with flam4 standalone
> program (same dialog, pixel corruption etc.). A restart is required to
> get the pixels to go away.
>
> If there is indeed a hard limit for flam4 based on the video card's
> memory, it'd be nice if it checked that before starting the render,
> and regardless it should probably force quit the rendering rather
> letting it proceed and corrupt video memory.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/fr0st/+bug/495986/+subscribe
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.