Crash on Eevee Rendering OpenGL issue ? #57708

New Issue

Bert Pauwels · 2018-11-08T16:56:14+01:00

Bert Pauwels commented

2018-11-08 16:56:14 +01:00

Since a few days Blender 2.8 is crashing when I try to render with Eevee. It's a simple scene with 6 primitives, a linked texture and normal map.
it works fine with Cycles though.
I got integrated gfx Intel HD 4000.

sysinfo:

Blender 2.80 (sub 30) System Information

Blender:

version: 2.80 (sub 30), branch: blender2.8, commit date: 2018-11-07 23:10, hash: a421cfa8d3, type: Release
build date: 07/11/2018, 17:03
platform: Windows

OpenGL:

renderer: 'Intel(R) HD Graphics 4000'
vendor: 'Intel'
version: '4.0.0 - Build 10.18.10.5059'

system-info.txt

log with --debug-gpu :

C:\Program Files\Blender Foundation\Blender 2.80>blender.exe --debug-gpu
Read prefs: C:\Users\user┬Á\AppData\Roaming\Blender Foundation\Blender\2.80\config\userpref.blend
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 192000hz instead
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Using KHR_debug extension
GL application marker: Successfully hooked OpenGL debug callback.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
found bundled python: C:\Program Files\Blender Foundation\Blender 2.80\2.80\python
Traceback (most recent call last):

File "C:\Program Files\Blender Foundation\Blender 2.80\2.80\scripts\modules\addon_utils.py", line 377, in enable
  raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")

Exception: Add-on 'camera_turnaround' has not been upgraded to 2.8, ignoring
GL API performance: Vertex shader recompiled due to state change.
Read blend: C:\repos\Blender\2.8\textures.blend
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported.
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF93A927D07
Module : C:\WINDOWS\SYSTEM32\ig7icd64.dll

C:\Program Files\Blender Foundation\Blender 2.80>

Since a few days Blender 2.8 is crashing when I try to render with Eevee. It's a simple scene with 6 primitives, a linked texture and normal map. it works fine with Cycles though. I got integrated gfx Intel HD 4000. sysinfo: **** # Blender 2.80 (sub 30) System Information **** Blender: **** version: 2.80 (sub 30), branch: blender2.8, commit date: 2018-11-07 23:10, hash: a421cfa8d31, type: Release build date: 07/11/2018, 17:03 platform: Windows OpenGL: **** renderer: 'Intel(R) HD Graphics 4000' vendor: 'Intel' version: '4.0.0 - Build 10.18.10.5059' [system-info.txt](https://archive.blender.org/developer/F5444089/system-info.txt) log with --debug-gpu : C:\Program Files\Blender Foundation\Blender 2.80>blender.exe --debug-gpu Read prefs: C:\Users\user┬Á\AppData\Roaming\Blender Foundation\Blender\2.80\config\userpref.blend AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 192000hz instead Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Using KHR_debug extension GL application marker: Successfully hooked OpenGL debug callback. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. found bundled python: C:\Program Files\Blender Foundation\Blender 2.80\2.80\python Traceback (most recent call last): ``` File "C:\Program Files\Blender Foundation\Blender 2.80\2.80\scripts\modules\addon_utils.py", line 377, in enable raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring") ``` Exception: Add-on 'camera_turnaround' has not been upgraded to 2.8, ignoring GL API performance: Vertex shader recompiled due to state change. Read blend: C:\repos\Blender\2.8\textures.blend Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Win32 Error# (3221692565): The specified OpenGL version and feature set are either invalid or not supported. Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF93A927D07 Module : C:\WINDOWS\SYSTEM32\ig7icd64.dll C:\Program Files\Blender Foundation\Blender 2.80>

Bert Pauwels commented

2018-11-08 16:56:14 +01:00

Added subscriber: @pauwels.bert

Wolfgang Faehnle commented

2018-11-08 17:00:55 +01:00

Added subscriber: @mib2berlin

Wolfgang Faehnle commented

2018-11-08 17:00:55 +01:00

Hi, can you please add the .blend with packed textures?
I have HD 4000 too and can test on Linux.

Hi, can you please add the .blend with packed textures? I have HD 4000 too and can test on Linux.

Bert Pauwels commented

2018-11-08 17:12:33 +01:00

Here you go.
Thanks in advance.

textures.blend

Here you go. Thanks in advance. [textures.blend](https://archive.blender.org/developer/F5444303/textures.blend)

Wolfgang Faehnle commented

2018-11-08 17:51:22 +01:00

I cant verify, open file > hit F12.

http://pasteall.org/pic/6ffd3a8c369495f35627faf1f84e708a

Opensuse Tumbleweed x86_64
CPU i7-3520M 8 GB
GPU Intel HD4000
KDE Plasma 5.13.5.11
Vivaldi 2.2.1360.4 (Official Build) snapshot (64-bit)

system-info.txt

I cant verify, open file > hit F12. http://pasteall.org/pic/6ffd3a8c369495f35627faf1f84e708a Opensuse Tumbleweed x86_64 CPU i7-3520M 8 GB GPU Intel HD4000 KDE Plasma 5.13.5.11 Vivaldi 2.2.1360.4 (Official Build) snapshot (64-bit) [system-info.txt](https://archive.blender.org/developer/F5444826/system-info.txt)

Bert Pauwels commented

2018-11-08 19:01:20 +01:00

This comment was removed by @pauwels.bert

*This comment was removed by @pauwels.bert*

Bert Pauwels commented

2018-11-08 19:11:02 +01:00

open and hit F12 works too on fresh install, after the render I try Shift+Z/ render in 3d view and it crashes again.
open and hit Shift+Z gives me black models in 3d view : http://www.blackcrow.eu/ss/blender_2018-11-08_19-07-55.png then hit F12 and it crashes
open and hit Shift+Z gives me black models in 3d view, assign the same material again via dropdown: http:*www.blackcrow.eu/ss/blender_2018-11-08_19-09-20.png and then it shows up properly in the 3d view: http:*www.blackcrow.eu/ss/blender_2018-11-08_19-10-13.png. Then I hit F12 and it crashes again.

Can you confirm Wolfgang ?

open and hit F12 works too on fresh install, after the render I try Shift+Z/ render in 3d view and it crashes again. open and hit Shift+Z gives me black models in 3d view : http://www.blackcrow.eu/ss/blender_2018-11-08_19-07-55.png then hit F12 and it crashes open and hit Shift+Z gives me black models in 3d view, assign the same material again via dropdown: http:*www.blackcrow.eu/ss/blender_2018-11-08_19-09-20.png and then it shows up properly in the 3d view: http:*www.blackcrow.eu/ss/blender_2018-11-08_19-10-13.png. Then I hit F12 and it crashes again. Can you confirm Wolfgang ?

Wolfgang Faehnle commented

2018-11-08 19:37:19 +01:00

Hi, I can verify black models after Shift+Z but I cant get Blender to crash.
If I hit Rendered View in the UI textures are properly shown.
May a Windows problem, need other Windows users to test.
Buildbot from today a421cfa8d3.

Hi, I can verify black models after Shift+Z but I cant get Blender to crash. If I hit Rendered View in the UI textures are properly shown. May a Windows problem, need other Windows users to test. Buildbot from today a421cfa8d31.

Bert Pauwels commented

2018-11-08 19:57:27 +01:00

thanks

Philipp Oeser commented

2018-11-09 11:38:38 +01:00

Added subscribers: @fclem, @lichtwerk

Clément Foucault was assigned by Philipp Oeser

2018-11-09 11:38:38 +01:00

Philipp Oeser commented

2018-11-09 11:38:38 +01:00

Cant reproduce (linux, nvidia 970m), so this seems tied to the HD 4000?

this thing should at least support OpenGL 4.0, but still we get this error

The specified OpenGL version and feature set are either invalid or not supported.

@fclem : does that ring a bell?

Cant reproduce (linux, nvidia 970m), so this seems tied to the HD 4000? - this thing should at least support OpenGL 4.0, but still we get this error > The specified OpenGL version and feature set are either invalid or not supported. @fclem : does that ring a bell?

Clément Foucault commented

2018-11-09 12:20:45 +01:00

Added subscriber: @mano-wii

Clément Foucault commented

2018-11-09 12:20:45 +01:00

The specified OpenGL version and feature set are either invalid or not supported.

This line is very misleading. It's only there because we try all opengl version starting from 4.5. If a version is not supported it try the previous one until it reaches the minimum 3.3 version.

We do that only on windows. So all theses lines are actually OK. I could replace them with more informative outputs.

Regarding the actual problem, I've testes on my HD 4600 on linux and it's working fine. The crash happen in the driver so it's a bit difficult to know what causes the problem. Perhaps @mano-wii can confirm this problem?

Black models are due to #55059.

> The specified OpenGL version and feature set are either invalid or not supported. This line is very misleading. It's only there because we try all opengl version starting from 4.5. If a version is not supported it try the previous one until it reaches the minimum 3.3 version. We do that only on windows. So all theses lines are actually OK. I could replace them with more informative outputs. Regarding the actual problem, I've testes on my HD 4600 on linux and it's working fine. The crash happen in the driver so it's a bit difficult to know what causes the problem. Perhaps @mano-wii can confirm this problem? Black models are due to #55059.

Bert Pauwels commented

2018-11-09 16:03:55 +01:00

further testing;
removed the material from the objects and gave it a new one, only difuse, removed all the uv maps, hit render and instant crash (Eevee)

further testing; removed the material from the objects and gave it a new one, only difuse, removed all the uv maps, hit render and instant crash (Eevee)

Germano Cavalcante commented

2018-11-09 20:59:57 +01:00

I can reproduce the bug on windows 64bits with Intel(R) HD Graphics 4000 and driver 4.0.0 - Build 10.18.10.4885.
Crash in glUseProgram with a program using the effect_ssr_frag.glsl shader and #define STEP_RESOLVE.
The crash is related to the get_scene_color function.
It is strange that this program works well in the 3dview. (Probably some status changes when entering the rendering context).

# Blender 2.80 (sub 30), Unknown revision

# backtrace
33: BLI_system_backtrace - 0x6D555120
32: sig_handle_crash_backtrace - 0x6BED3EC0
31: sig_handle_crash - 0x6BED3F10
30: windows_exception_handler - 0x6BED4160
29: UnhandledExceptionFilter - 0x12EFBB60
28: memset - 0x16AC0AC0
27: _C_specific_handler - 0x16AAAAA0
26: _chkstk - 0x16ABEC10
25: RtlWalkFrameChain - 0x16A25890
24: KiUserExceptionDispatcher - 0x16ABDC30
23: RegisterProcTableCallback - 0xB8F6C210
22: RegisterProcTableCallback - 0xB8F6C210
21: RegisterProcTableCallback - 0xB8F6C210
20: GPU_shader_bind - 0x6CA2C390
19: draw_shgroup - 0x6CAAFBE0
18: drw_draw_pass_ex - 0x6CAB0BE0
17: DRW_draw_pass - 0x6CAAC2B0
16: EEVEE_reflection_compute - 0x6CB2F8B0
15: EEVEE_render_draw - 0x6CB04AA0
14: eevee_render_to_image - 0x6CAE69E0
13: DRW_render_to_image - 0x6CA55D70
12: RE_engine_render - 0x6C6E1960
11: do_render_3d - 0x6C6F5AB0
10: do_render - 0x6C6F5E70
9: do_render_composite - 0x6C6F6520
8: do_render_all_options - 0x6C6F70E0
7: RE_BlenderFrame - 0x6C6F2580
6: render_startjob - 0x6C58DE40
5: do_job_thread - 0x6BF1CBD0
4: tslot_thread_start - 0x6D5547B0
3: pthread_key_delete - 0x2241460
2: o_ceil - 0x136BC480
1: BaseThreadInitThunk - 0x13EC3020
0: RtlUserThreadStart - 0x16A91440

Apparently it is possible to keep one of the lines that has textureLod but not both at the same time.

EDIT:
After further investigation I realized that crash is avoided when any of the uniforms sampler[...] is not used.
Therefore, if it is possible to remove at least one of the uniforms sampler..., the problem would be fixed.

I can reproduce the bug on `windows 64bits` with `Intel(R) HD Graphics 4000` and driver `4.0.0 - Build 10.18.10.4885`. Crash in `glUseProgram` with a program using the `effect_ssr_frag.glsl` shader and `#define STEP_RESOLVE`. The crash is related to the `get_scene_color` function. It is strange that this program works well in the 3dview. (Probably some status changes when entering the rendering context). ``` # Blender 2.80 (sub 30), Unknown revision # backtrace 33: BLI_system_backtrace - 0x6D555120 32: sig_handle_crash_backtrace - 0x6BED3EC0 31: sig_handle_crash - 0x6BED3F10 30: windows_exception_handler - 0x6BED4160 29: UnhandledExceptionFilter - 0x12EFBB60 28: memset - 0x16AC0AC0 27: _C_specific_handler - 0x16AAAAA0 26: _chkstk - 0x16ABEC10 25: RtlWalkFrameChain - 0x16A25890 24: KiUserExceptionDispatcher - 0x16ABDC30 23: RegisterProcTableCallback - 0xB8F6C210 22: RegisterProcTableCallback - 0xB8F6C210 21: RegisterProcTableCallback - 0xB8F6C210 20: GPU_shader_bind - 0x6CA2C390 19: draw_shgroup - 0x6CAAFBE0 18: drw_draw_pass_ex - 0x6CAB0BE0 17: DRW_draw_pass - 0x6CAAC2B0 16: EEVEE_reflection_compute - 0x6CB2F8B0 15: EEVEE_render_draw - 0x6CB04AA0 14: eevee_render_to_image - 0x6CAE69E0 13: DRW_render_to_image - 0x6CA55D70 12: RE_engine_render - 0x6C6E1960 11: do_render_3d - 0x6C6F5AB0 10: do_render - 0x6C6F5E70 9: do_render_composite - 0x6C6F6520 8: do_render_all_options - 0x6C6F70E0 7: RE_BlenderFrame - 0x6C6F2580 6: render_startjob - 0x6C58DE40 5: do_job_thread - 0x6BF1CBD0 4: tslot_thread_start - 0x6D5547B0 3: pthread_key_delete - 0x2241460 2: o_ceil - 0x136BC480 1: BaseThreadInitThunk - 0x13EC3020 0: RtlUserThreadStart - 0x16A91440 ``` Apparently it is possible to keep one of the lines that has `textureLod` but not both at the same time. EDIT: After further investigation I realized that crash is avoided when any of the uniforms sampler[...] is not used. Therefore, if it is possible to remove at least one of the uniforms sampler..., the problem would be fixed.

Germano Cavalcante commented

2018-11-13 14:14:09 +01:00

The crash occurs when you call glUseProgram with some programs made in another glcontext;
I found 3 programs with the same problem (one with shader effect_ssr_frag.glsl, one with lightprobe_planar_display_frag.glsl, and one with effect_downsample_frag.glsl);
They all have at least one uniform of texture;
Two of them have the uniform sampler2DArray probePlanars;
The other only has the uniform sampler2D source;
No matter when the program is called the crash always occurs in the other glcontext.
The program with the effect_ssr_frag.glsl shader can be solved if one of the uniforms samplers is removed from it.

I could not check if the problem occurs in the same glcontext but in a different thread.
This is obviously a problem with the Intel driver, so maybe the only solution is to wait for an update in the driver that solves this problem :\

1. The crash occurs when you call `glUseProgram` with some programs made in another glcontext; 2. I found 3 programs with the same problem (one with shader `effect_ssr_frag.glsl`, one with `lightprobe_planar_display_frag.glsl`, and one with `effect_downsample_frag.glsl`); 3. They all have at least one uniform of texture; 4. Two of them have the `uniform sampler2DArray probePlanars`; 5. The other only has the `uniform sampler2D source`; 6. No matter when the program is called the crash always occurs in the other glcontext. 7. The program with the `effect_ssr_frag.glsl` shader can be solved if one of the uniforms samplers is removed from it. I could not check if the problem occurs in the same glcontext but in a different thread. This is obviously a problem with the Intel driver, so maybe the only solution is to wait for an update in the driver that solves this problem :\

Germano Cavalcante commented

2018-11-13 19:22:25 +01:00

Changed status from 'Open' to: 'Resolved'

Germano Cavalcante closed this issue

2018-11-13 19:22:25 +01:00

Germano Cavalcante commented

2018-11-13 19:22:25 +01:00

Solved by c39d5a6c88

Solved by c39d5a6c88

Sign in to join this conversation.