Blender 2.8 eevee crashes when I try to increase shadow cube size and hit render #55888

New Issue

Monsour Leyco · 2018-07-10T14:14:30+02:00

Monsour Leyco commented

2018-07-10 14:14:30 +02:00

System Information
Machine: Lenovo g40-60
OS: Windows 10 Single Language
Graphics: AMD Radeon R5 M230 / Intel(R) HD Graphics 5500
CPU: Intel(R) Core(TM) i7-5500U CPU @2.40GHz
Ram: 8GB

Blender Version
Branch: blender2.8
Hash: 1112f49
Date: 2018-07-09 22:47

Short description of error
Render engine: Eevee
Whenever I try to increase the Cube Size on the Shadow Panel higher than 512px and hit the Rendered Preview or Render Image blender crashes.

Exact steps for others to reproduce the error

Open Blender
Select Render Tab
Open the Shadows Panel
Click the dropdown for the Cube Size
Choose a value higher than 512px
Hit render/render preview

**System Information** Machine: Lenovo g40-60 OS: Windows 10 Single Language Graphics: AMD Radeon R5 M230 / Intel(R) HD Graphics 5500 CPU: Intel(R) Core(TM) i7-5500U CPU @2.40GHz Ram: 8GB **Blender Version** Branch: blender2.8 Hash: 1112f49 Date: 2018-07-09 22:47 **Short description of error** Render engine: Eevee Whenever I try to increase the Cube Size on the Shadow Panel higher than 512px and hit the Rendered Preview or Render Image blender crashes. **Exact steps for others to reproduce the error** 1. Open Blender 2. Select Render Tab 3. Open the Shadows Panel 4. Click the dropdown for the Cube Size 5. Choose a value higher than 512px 6. Hit render/render preview

Monsour Leyco commented

2018-07-10 14:14:30 +02:00

Added subscriber: @monsourleyco

blender-admin commented

2018-07-10 14:14:30 +02:00

#56076 was marked as duplicate of this issue

Brecht Van Lommel commented

2018-07-10 18:11:38 +02:00

Added subscriber: @brecht

Clément Foucault was assigned by Brecht Van Lommel

2018-07-10 18:11:38 +02:00

Brecht Van Lommel commented

2018-07-10 18:11:38 +02:00

Confirmed on AMD RX Vega on Windows, GTX 1080 on Linux works fine.

Console shows:

GPUTexture: texture alloc failed. Not enough Video Memory. Error      : EXCEPTION_ACCESS_VIOLATION

It would be nice to not crash when running out of memory, but also probably it shouldn't be happening in the first place for such a simple change.

Confirmed on AMD RX Vega on Windows, GTX 1080 on Linux works fine. Console shows: ``` GPUTexture: texture alloc failed. Not enough Video Memory. Error : EXCEPTION_ACCESS_VIOLATION ``` It would be nice to not crash when running out of memory, but also probably it shouldn't be happening in the first place for such a simple change.

Alexandre commented

2018-07-12 22:05:22 +02:00

Added subscriber: @Snowpz

s12a commented

2018-07-16 16:00:43 +02:00

Added subscriber: @s12a

Brecht Van Lommel commented

2018-07-22 11:48:34 +02:00

Added subscriber: @Radicant

Clément Foucault commented

2018-07-27 12:01:22 +02:00

So a follow up to my investigation: The use of GL_PROXY_TEXTURE2D/3D must be buggy on the AMD driver on windows. So I'm tempted to remove the check entirely, or blacklist it for this driver.

Why is it buggy? Because any texture 2D array of size > 2048 in width & height (and 1 layer) is considered invalid even if it is actually supported (removing the check without any crash or error).

The proxy texture mechanism seems to be very old and not widely used.

This check does not even prevent Out Of Memory issue it just states that the OGL implementation can support this texture.

@brecht opengl can only run out of memory if both VRAM and RAM is full (because of virtual memory blabla). The only thing that can make a texture bug is when there is not enough device memory to have all the current drawcall's textures resident (in the VRAM). And this is out of our hand because it's the drivers responsability.

So a follow up to my investigation: The use of GL_PROXY_TEXTURE2D/3D must be buggy on the AMD driver on windows. So I'm tempted to remove the check entirely, or blacklist it for this driver. Why is it buggy? Because any texture 2D array of size > 2048 in width & height (and 1 layer) is considered invalid even if it is actually supported (removing the check without any crash or error). The proxy texture mechanism seems to be very old and not widely used. This check does not even prevent Out Of Memory issue it just states that the OGL implementation can support this texture. @brecht opengl can only run out of memory if both VRAM and RAM is full (because of virtual memory blabla). The only thing that can make a texture bug is when there is not enough device memory to have all the current drawcall's textures resident (in the VRAM). And this is out of our hand because it's the drivers responsability.

Brecht Van Lommel commented

2018-07-27 12:33:13 +02:00

Just remove the proxy checks I think, I agree it's not useful as a way to avoid out of memory errors.

We could keep the rescaling if the resolution exceeds GL_MAX_TEXTURE_SIZE, GL_MAX_3D_TEXTURE_SIZE, GL_MAX_CUBE_MAP_TEXTURE_SIZE perhaps.

Just remove the proxy checks I think, I agree it's not useful as a way to avoid out of memory errors. We could keep the rescaling if the resolution exceeds GL_MAX_TEXTURE_SIZE, GL_MAX_3D_TEXTURE_SIZE, GL_MAX_CUBE_MAP_TEXTURE_SIZE perhaps.

Clément Foucault commented

2018-07-27 13:53:33 +02:00

Actually I think I found why this happen.

The driver must treat GL_PROXY_TEXTURE_2D_ARRAY as a GL_PROXY_TEXTURE_3D and apply the same limitation to it, so width, height and depth are checked against GL_MAX_3D_TEXTURE_SIZE.
But following the spec width and height should be checked against GL_MAX_TEXTURE_SIZE which is given to be much larger.

I'll commit a general fix.

Actually I think I found why this happen. The driver must treat GL_PROXY_TEXTURE_2D_ARRAY as a GL_PROXY_TEXTURE_3D and apply the same limitation to it, so width, height and depth are checked against GL_MAX_3D_TEXTURE_SIZE. But following the spec width and height should be checked against GL_MAX_TEXTURE_SIZE which is given to be much larger. I'll commit a general fix.

blender-admin commented

2018-07-27 13:56:07 +02:00

This issue was referenced by 141e94f87f

This issue was referenced by 141e94f87ff29452ed8df82b4c25d8d134a34dad

Clément Foucault commented

2018-07-27 13:58:52 +02:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2018-07-27 13:58:52 +02: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

Blender 2.8 eevee crashes when I try to increase shadow cube size and hit render #55888