Blender-4.0.0-beta - Does not stay open - Crashes Instantly #113124

New Issue

Trevor H · 2023-10-01T18:18:42+02:00

Trevor H commented

2023-10-01 18:18:42 +02:00

System Information
Operating system: Windows 10 home : Laptop Lenovo G50-80
Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171

Blender Version
Broken: Blender-4.0.0-beta+v40.3f633503d34e-windows.amd64-release
Worked: #111643 ,..... with 'Blender_debug_gpu_glitchworkaround', but with shader viewport problem.

Short description of error
Blender-4.0.0-beta+v40.3f633503d34e-windows.amd64-release, does not stay open with the main Blender Icon Application, or with 'Blender_debug_gpu_glitchworkaround'. Blender 4.0 beta will crash Instantly.

Exact steps for others to reproduce the error
Same as Short description of error

**System Information** Operating system: Windows 10 home : Laptop Lenovo G50-80 Graphics card: Intel(R) HD Graphics 5500 4.4.0 - Build 20.19.15.5171 **Blender Version** Broken: Blender-4.0.0-beta+v40.3f633503d34e-windows.amd64-release Worked: https://projects.blender.org/blender/blender/pulls/111643 ,..... with 'Blender_debug_gpu_glitchworkaround', but with shader viewport problem. **Short description of error** Blender-4.0.0-beta+v40.3f633503d34e-windows.amd64-release, does not stay open with the main Blender Icon Application, or with 'Blender_debug_gpu_glitchworkaround'. Blender 4.0 beta will crash Instantly. **Exact steps for others to reproduce the error** Same as Short description of error

blender_system_info.txt

12 KiB

blender_debug_output.txt

36 KiB

Trevor H added the

labels 2023-10-01 18:18:43 +02:00

Pratik Borhade commented

2023-10-02 06:10:51 +02:00

Hi, thanks for the report. Could you also share C:\Users\User~1\AppData\Local\Temp\blender.crash.txt?
Your GPU is still supported I believe (OpenGL 4.4 and Broadwell architecture)

Hi, thanks for the report. Could you also share `C:\Users\User~1\AppData\Local\Temp\blender.crash.txt`? Your GPU is still supported I believe (OpenGL 4.4 and Broadwell architecture)

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-10-02 06:11:01 +02:00

Trevor H commented

2023-10-02 11:59:25 +02:00

@PratikPB2123

Here are the crash reports.

. Blender icon application - Crash txt
. Blender_debug_gpu_glitchworkaround - Crash txt

I saved both in case there is something different in them - The Blender icon application has never opened, when I tried any version of Blender 4.0.

@PratikPB2123 Here are the crash reports. . Blender icon application - Crash txt . Blender_debug_gpu_glitchworkaround - Crash txt I saved both in case there is something different in them - The Blender icon application has never opened, when I tried any version of Blender 4.0.

blender - Icon application.crash.txt

19 KiB

blender_debug_gpu_glitchworkaround.crash.txt

19 KiB

Pratik Borhade commented

2023-10-02 12:37:40 +02:00

@pragma37 @Jeroen-Bakker can you check?

Pratik Borhade added

Status

Needs Info from Developers

and removed

Status

Needs Information from User

labels 2023-10-02 12:37:48 +02:00

Miguel Pozo added the

Module

EEVEE & Viewport

label 2023-10-02 12:47:31 +02:00

Pratik Borhade referenced this issue

2023-10-13 05:27:46 +02:00

blender 4.0 beta not working on Intel® HD Graphics 5500 #113567

Jeroen Bakker commented

2023-10-13 05:57:50 +02:00

It fails in the first OpenGL command. I don’t have the GPU or similar. So not easy to solve.

Would advice to monitor the issue. Ensure that the driver from the Intel website is installed. Sometimes the default driver of a laptop contains bugs and are not regularly updated.

@memento do you have a similar device?

It fails in the first OpenGL command. I don’t have the GPU or similar. So not easy to solve. Would advice to monitor the issue. Ensure that the driver from the Intel website is installed. Sometimes the default driver of a laptop contains bugs and are not regularly updated. @memento do you have a similar device?

Anton Raves commented

2023-10-13 06:31:52 +02:00

@Jeroen-Bakker Just checked, unfortunately I do not have access to a machine with an Intel HD 5500...

Trevor H commented

2023-10-13 19:26:32 +02:00

@Jeroen-Bakker

"Ensure that the driver from the Intel website is installed. Sometimes the default driver of a laptop contains bugs and are not regularly updated."

Just to add the 'Build 20.19.15.5171' is from Intel website. The Laptop drivers are way out of date, and they stopped updating it.

@Jeroen-Bakker "Ensure that the driver from the Intel website is installed. Sometimes the default driver of a laptop contains bugs and are not regularly updated." Just to add the 'Build 20.19.15.5171' is from Intel website. The Laptop drivers are way out of date, and they stopped updating it.

👍 1

Pratik Borhade referenced this issue

2023-10-18 09:03:15 +02:00

blender 4.1 not opening #113877

R commented

2023-11-17 14:41:38 +01:00

I also have a crash on Lenovo T450s laptop:
Win10 pro, Blender 4.0 stable.
Intel(R) HD Graphics 5500
Driver 20.19.15.5144

ERROR (gpu.shader): draw_command_generate Linking:
| Out of resource error.

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF616E5813B
Module : blender.exe
Thread : 00001258

I also have a crash on Lenovo T450s laptop: Win10 pro, Blender 4.0 stable. Intel(R) HD Graphics 5500 Driver 20.19.15.5144 ERROR (gpu.shader): draw_command_generate Linking: | Out of resource error. Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF616E5813B Module : blender.exe Thread : 00001258

blender.crash.txt

19 KiB

Pratik Borhade referenced this issue

2023-11-19 13:33:17 +01:00

blender 4.0.1 isn't starting #115132

Thomas Dinges referenced this issue

2023-11-19 16:49:21 +01:00

Blender 4.01 crash "EXCEPTION_ACCESS_VIOLATION" #115144

Jeroen Bakker commented

2023-11-20 11:56:42 +01:00

Can someone add a system info.txt (generated from Blender 3.6) so I can try to isolate what resource it is complaining about?
Also add a report (from Blender 4.0.1) with debug info by starting blender_debug_gpu from the installation folder.

Can someone add a system info.txt (generated from Blender 3.6) so I can try to isolate what resource it is complaining about? Also add a report (from Blender 4.0.1) with debug info by starting blender_debug_gpu from the installation folder.

Trevor H commented

2023-11-20 12:32:09 +01:00

@Jeroen-Bakker

Hope this is what you need!

@Jeroen-Bakker Hope this is what you need!

blender_debug_output.txt

18 KiB

blender_system_info.txt

12 KiB

Blender 3.6 system-info.txt

39 KiB

Miguel Pozo commented

2023-11-20 13:03:29 +01:00

I think this may be caused by the supported number SSBO bindings.

ERROR (gpu.shader): draw_command_generate Linking: 
      | Out of resource error.

We target hardware with at least 12 SSBO slots, but I don't think that limit is checked at startup.

I think this may be caused by the supported number SSBO bindings. ``` ERROR (gpu.shader): draw_command_generate Linking: | Out of resource error. ``` We target hardware with at least 12 SSBO slots, but I don't think that limit is checked at startup.

Jeroen Bakker commented

2023-11-20 14:00:57 +01:00

Currently it is set to 8. IIRC 12 was an 4.1 limitation.

https://projects.blender.org/blender/blender/src/branch/main/source/blender/gpu/opengl/gl_backend.cc#L183

These devices seems to support 16. http://opengl.gpuinfo.org/displayreport.php?id=1035

Not saying this isn't the issue, but needs more research.

Currently it is set to 8. IIRC 12 was an 4.1 limitation. https://projects.blender.org/blender/blender/src/branch/main/source/blender/gpu/opengl/gl_backend.cc#L183 These devices seems to support 16. http://opengl.gpuinfo.org/displayreport.php?id=1035 Not saying this isn't the issue, but needs more research.

Miguel Pozo commented

2023-11-20 15:28:10 +01:00

Currently it is set to 8. IIRC 12 was an 4.1 limitation.

Nope, check draw_command_generate (DRW_RESOURCE_ID_SLOT).

But yes, it may be something else.
I found this and it certainly doesn't look like an SSBO limit issue.
The error message is far from helpful.

> Currently it is set to 8. IIRC 12 was an 4.1 limitation. Nope, check `draw_command_generate` (`DRW_RESOURCE_ID_SLOT`). But yes, it may be something else. I found [this](https://community.intel.com/t5/Developing-Games-on-Intel/OpenGL-compute-shader-on-HD4600-quot-Out-of-resource-error-quot/m-p/1238926) and it certainly doesn't look like an SSBO limit issue. The error message is far from helpful.

👍 1

Jeroen Bakker commented

2023-11-20 15:58:01 +01:00

Is it possible for anyone to install 20.19.15.4624 and test if that fixes the issue for us as well?

Trevor H commented

2023-11-20 20:13:36 +01:00

@Jeroen-Bakker

Can you share the link to download. Been looking online for the driver had no luck in finding it.

@Jeroen-Bakker Can you share the link to download. Been looking online for the driver had no luck in finding it.

Trevor H commented

2023-11-20 20:37:40 +01:00

Out of curiosity I tried my Laptop Lenovo G50-80 original graphic drivers. 20.19.15.4835

Blender 4.0.1 opened without any issues!

Edit: All The Viewport shading work as well.

Out of curiosity I tried my Laptop Lenovo G50-80 original graphic drivers. 20.19.15.4835 Blender 4.0.1 opened without any issues! Edit: All The Viewport shading work as well.

Blender 4.jpg

216 KiB

❤️ 1

Jeroen Bakker commented

2023-11-21 09:39:57 +01:00

For the HD 4000/5000 series devices we could detect the faulty drivers and show the unsupported platform dialog. And we should document that older drivers might work. For actually developing a workaround we need physical access to those devices, which we don't have.

Note; looking a bit more in the future I expect these devices can still be used for based modelling using workbench. Rendering using EEVEE might become complicated as 4.1 target features that are known not to be performant on HD iGPUs.

For the HD 4000/5000 series devices we could detect the faulty drivers and show the unsupported platform dialog. And we should document that older drivers might work. For actually developing a workaround we need physical access to those devices, which we don't have. Note; looking a bit more in the future I expect these devices can still be used for based modelling using workbench. Rendering using EEVEE might become complicated as 4.1 target features that are known not to be performant on HD iGPUs. - https://projects.blender.org/blender/blender-manual/pulls/104638 - https://projects.blender.org/blender/blender/pulls/115228

👍 1

Jeroen Bakker referenced this issue from blender/blender-manual

2023-11-21 10:17:50 +01:00

Intel HD4000/5000 Drivers #104638

Jeroen Bakker referenced this issue

2023-11-21 10:32:28 +01:00

OpenGL: Mark Legacy Intel Drivers Unsupported #115228

Jeroen Bakker referenced this issue from a commit

2023-11-21 10:52:32 +01:00

Intel HD4000/5000 Drivers

Jeroen Bakker referenced this issue from a commit

2023-11-21 10:53:29 +01:00

Intel HD4000/5000 Drivers

Jeroen Bakker referenced this issue from a commit

2023-11-23 08:00:32 +01:00

OpenGL: Mark Legacy Intel Drivers Unsupported

Jeroen Bakker commented

2023-11-23 08:04:22 +01:00

All changes landed in 4.1. If we do a 4.0.2 release these changes will be included as well. Closing this issue.
@TH-10 Thanks for testing and providing feedback!

All changes landed in 4.1. If we do a 4.0.2 release these changes will be included as well. Closing this issue. @TH-10 Thanks for testing and providing feedback!

❤️ 1

Jeroen Bakker closed this issue

2023-11-23 08:04:25 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Info from Developers

labels 2023-11-23 08:04:27 +01:00

Thomas Dinges referenced this issue from a commit

2023-11-27 18:00:02 +01:00