Eevee out of GPU memory on large render #70305

New Issue

Sorin Vinatoru · 2019-09-27T20:28:40+02:00

Sorin Vinatoru commented

2019-09-27 20:28:40 +02:00

We ran into a weird issue with Eevee and a large render. It seems to run out of memory at 480 MB on a video card with 12 GB memory. This seems to happen when allocating the memory for the render result image.

Not sure if this is about the texture slot memory limit, but I'll paste the log below.

If it's a texture slot memory issue, then the bug is when rendering with border render. Even if a border render is set, it will still allocate the full image size for the final render. It crashes with the exact same error even if there's a border render set in the file.

So two questions here:

Why it runs out of memory?
Why is it trying to allocate the entire image when there's a border + crop set?

Here's the log:

GPUTexture: create : TEXTURE_2D, DEPTH24_STENCIL8, w : 7200, h : 18000, d : 0, comp : 1, size : 494.38 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 494.38 MiB.
Writing: /tmp/Victoria_Art.crash.txt
Segmentation fault (core dumped)

We ran into a weird issue with Eevee and a large render. It seems to run out of memory at 480 MB on a video card with 12 GB memory. This seems to happen when allocating the memory for the render result image. Not sure if this is about the texture slot memory limit, but I'll paste the log below. If it's a texture slot memory issue, then the bug is when rendering with border render. Even if a border render is set, it will still allocate the full image size for the final render. It crashes with the exact same error even if there's a border render set in the file. So two questions here: 1. Why it runs out of memory? 2. Why is it trying to allocate the entire image when there's a border + crop set? Here's the log: ``` GPUTexture: create : TEXTURE_2D, DEPTH24_STENCIL8, w : 7200, h : 18000, d : 0, comp : 1, size : 494.38 MiB GPUTexture: texture alloc failed. Likely not enough Video Memory. Current texture memory usage : 494.38 MiB. Writing: /tmp/Victoria_Art.crash.txt Segmentation fault (core dumped) ```

Sorin Vinatoru commented

2019-09-27 20:28:40 +02:00

Added subscriber: @sorinv

Sorin Vinatoru commented

2019-09-27 20:29:27 +02:00

Forgot to mention, this is affecting Blender 2.80 official release.

We're rendering with Ubuntu 18.04 LTS, command line render.

Forgot to mention, this is affecting Blender 2.80 official release. We're rendering with Ubuntu 18.04 LTS, command line render.

Sorin Vinatoru changed title from ~~Eevee out og GPU memory on large render~~ to Eevee out of GPU memory on large render

2019-09-27 20:30:40 +02:00

noki paike commented

2019-09-27 20:54:08 +02:00

Added subscriber: @nokipaike

noki paike commented

2019-09-27 20:54:08 +02:00

without a reference file, a video or other, how do you expect them to solve your problem ??

Zachary Russ commented

2019-09-27 21:10:39 +02:00

Added subscriber: @KlariceVulpes

Zachary Russ commented

2019-09-27 21:10:39 +02:00

bug.blend I've created a blend file with the issue.

[bug.blend](https://archive.blender.org/developer/F7777491/bug.blend) I've created a blend file with the issue.

noki paike commented

2019-09-27 21:46:15 +02:00

@KlariceVulpes are you sure this file is related to the problem shown?
I opened the blender file, it tells me that it is only 34 mb and windows 214 mb, eevee is slow for some reason, but I don't see memory leaks ...
my gpu is a radeon 7600 HD , uses blender workarounds, on windows 10

pesant.mp4

edit:

I realized that the cube with the volumetric does not refresh (volumetric problem on my gpu.) #70091
maybe it's related to this? that the samples of volumetrics are going out of control with memory leack? (not on my machine, so i didn't noticed this problem)

@KlariceVulpes are you sure this file is related to the problem shown? I opened the blender file, it tells me that it is only 34 mb and windows 214 mb, eevee is slow for some reason, but I don't see memory leaks ... my gpu is a radeon 7600 HD , uses blender workarounds, on windows 10 [pesant.mp4](https://archive.blender.org/developer/F7777515/pesant.mp4) edit: I realized that the cube with the volumetric does not refresh (volumetric problem on my gpu.) #70091 maybe it's related to this? that the samples of volumetrics are going out of control with memory leack? (not on my machine, so i didn't noticed this problem)

Sorin Vinatoru commented

2019-09-27 21:50:38 +02:00

I can fully reproduce this both on my windows computer (Nvidia GTX 980) and on our Linux servers (Nvidia K80). It may be a Nvidia only issue.

Sorin Vinatoru commented

2019-09-27 21:53:12 +02:00

You may also want to hit F12. Using viewport rendering does not reproduce the error on my machine. Hitting F12 will crash Blender instantly.

noki paike commented

2019-09-27 21:57:00 +02:00

@sorinv do you think it's related to the volumetrics in that file?

noki paike commented

2019-09-27 22:00:50 +02:00

ok i pressed f12, blender devoured the memory, blender didn't crash, but it was freeze and then i had to kill it myself.

Roger B commented

2019-09-28 03:48:24 +02:00

Added subscriber: @rboxman

Roger B commented

2019-09-28 03:48:24 +02:00

Why it doesn't use the 30% you have set in render properties might be the primary bug here. Manually shrinking your initial dimensions to 2100x5400 works
It's odd why blender eats up resources and typically needs to be manually killed in this instance... still needs investigated I suppose
It may never be able to render at that 18000 dimension (100%) in any case. OpenGL GL_MAX_TEXTURE_SIZE limits on my AMD FirePro W2100 card is 16384 and I'm not aware of any implementation that allows higher than that.

1. Why it doesn't use the 30% you have set in render properties might be the primary bug here. Manually shrinking your initial dimensions to 2100x5400 works 2. It's odd why blender eats up resources and typically needs to be manually killed in this instance... still needs investigated I suppose 3. It may never be able to render at that 18000 dimension (100%) in any case. OpenGL GL_MAX_TEXTURE_SIZE limits on my AMD FirePro W2100 card is 16384 and I'm not aware of any implementation that allows higher than that.

Zachary Russ commented

2019-09-28 03:56:55 +02:00

It seems odd that it will still crash if using a custom border on the full resolution, though. Like Sorin asked, is Blender still trying to allocate that massive 18000 dimension even with the custom border in place? If it is, I feel like that would be a bug. Is it not?

Philipp Oeser commented

2019-11-21 14:07:37 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-11-21 14:07:37 +01:00

Just noticed we also have #71692 (Eevee allocates entire render framebuffer texture for region renders) now, will merge these reports...

Philipp Oeser commented

2019-11-21 14:07:45 +01:00

Closed as duplicate of #71692

Philipp Oeser closed this issue

2019-11-21 14:07:45 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Eevee out of GPU memory on large render #70305