Blender crashes as soon as an image texture is plugged in the material BSDF node #108868

New Issue

TheArtySquid · 2023-06-11T21:30:58+02:00

TheArtySquid commented

2023-06-11 21:30:58 +02:00

System Information
Operating system: Windows 10
Graphics card: NVIDIA GeForce GTX 1080 Ti
See attached log for more detail

Blender Version
Broken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions
Worked: ??? The earliest available build, 2.93.18, also causes the same crash

Short description of error
The second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes

Similar tickets
#76193
#76377

Exact steps for others to reproduce the error

Start Blender.
Create new default file.
Select the default cube.
Switch to Shading workspace.
Add Image Texture node.
Create new image or select an existing one.
Plug Color output to the Base Color input of the Principled BSDF node.
Watch Blender shut down.

**System Information** Operating system: Windows 10 Graphics card: NVIDIA GeForce GTX 1080 Ti See attached log for more detail **Blender Version** Broken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions Worked: ??? The earliest available build, 2.93.18, also causes the same crash **Short description of error** The second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes **Similar tickets** #76193 #76377 **Exact steps for others to reproduce the error** 1. Start Blender. 2. Create new default file. 3. Select the default cube. 4. Switch to Shading workspace. 5. Add Image Texture node. 6. Create new image or select an existing one. 7. Plug Color output to the Base Color input of the Principled BSDF node. 8. Watch Blender shut down.

blender_debug_output.txt

3.5 KiB

blender_system_info.txt

22 KiB

TheArtySquid added the

labels 2023-06-11 21:30:59 +02:00

Jesse Yurkovich commented

2023-06-11 21:46:25 +02:00

This is most likely because you're using a custom OCIO configuration; one that is not compatable with what Blender expects. From your log files:

Color management: Using C:\ProgramData\Redshift\Data\OCIO\config.ocio as a configuration file
Color management: Error could not find role texture_paint role.
Color management: Error could not find role default_byte role.
Color management: scene view "Filmic" not found, setting default "ACES 1.0 SDR-video".
...

Writing:  @C:\Users\emili\AppData\Local\Temp\blender.crash.txt

Those "Errors" are important and need to be fixed for Blender to function properly.

To be sure, please attach your C:\Users\emili\AppData\Local\Temp\blender.crash.txt which will most likely detail that it's crashing because the color management configuration is incorrect.

This is most likely because you're using a custom OCIO configuration; one that is not compatable with what Blender expects. From your log files: ``` Color management: Using C:\ProgramData\Redshift\Data\OCIO\config.ocio as a configuration file Color management: Error could not find role texture_paint role. Color management: Error could not find role default_byte role. Color management: scene view "Filmic" not found, setting default "ACES 1.0 SDR-video". ... Writing: @C:\Users\emili\AppData\Local\Temp\blender.crash.txt ``` Those "Errors" are important and need to be fixed for Blender to function properly. To be sure, please attach your `C:\Users\emili\AppData\Local\Temp\blender.crash.txt` which will most likely detail that it's crashing because the color management configuration is incorrect.

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-06-11 21:46:33 +02:00

TheArtySquid commented

2023-06-11 23:18:26 +02:00

Thanks for the quick response, here's the crash text file.

If the issue is as you describe, I could see OCIO becoming a headache: my current config file is a default one that came with rendering for Redshift, so I wouldn't want to solve Blender problems at the cost of causing similar issues in my other softwares.

Thanks for the quick response, here's the crash text file. If the issue is as you describe, I could see OCIO becoming a headache: my current config file is a default one that came with rendering for Redshift, so I wouldn't want to solve Blender problems at the cost of causing similar issues in my other softwares.

blender.crash.txt

25 KiB

Jesse Yurkovich commented

2023-06-11 23:28:51 +02:00

Yeah, it's crashing in color management:

blender.exe         :0x00007FF7890D30D0  colormanage_ensure_srgb_scene_linear_info
blender.exe         :0x00007FF7890D1A30  IMB_colormanagement_space_is_scene_linear
blender.exe         :0x00007FF7890F3B00  IMB_create_gpu_texture
blender.exe         :0x00007FF788E353E0  image_get_gpu_texture
blender.exe         :0x00007FF7890487F0  DRW_shgroup_add_material_resources

That Blender is picking up this file means that the Redshift install most likely set the "OCIO" environment variable system wide.

What you can do instead is launch blender with that environment variable blanked out. Since you're launching Blender through Steam though, I'm not sure what this would look like. Or investigate ways to specify the config file in Redshift directly, without resorting to having to use the environment variable at all.

Yeah, it's crashing in color management: ``` blender.exe :0x00007FF7890D30D0 colormanage_ensure_srgb_scene_linear_info blender.exe :0x00007FF7890D1A30 IMB_colormanagement_space_is_scene_linear blender.exe :0x00007FF7890F3B00 IMB_create_gpu_texture blender.exe :0x00007FF788E353E0 image_get_gpu_texture blender.exe :0x00007FF7890487F0 DRW_shgroup_add_material_resources ``` That Blender is picking up this file means that the Redshift install most likely set the "OCIO" environment variable system wide. What you can do instead is launch blender with that environment variable blanked out. Since you're launching Blender through Steam though, I'm not sure what this would look like. Or investigate ways to specify the config file in Redshift directly, without resorting to having to use the environment variable at all.

👀 1

TheArtySquid commented

2023-06-11 23:39:36 +02:00

Ok thanks, I will look in that direction and report how it goes

TheArtySquid commented

2023-06-12 09:28:00 +02:00

Alright, Blender problem solved - kinda. I followed the procedure to install ACES1.2 with a system-wide variable for the OCIO config that replaces the Redshift custom one and the crashes do not happen anymore.

From a user point of view, it would be nice if in future versions the issue was met with an error message warning about color management issues rather than a crash.

On a secondary note the update is now causing issues in Redshift, which in theory should be able to use a separate OCIO config I specified - in practice it seems to have its internal color space categories messed up by the new system environment variable. I will look further into this but I don't think it should be any concern for Blender devs.

One possible compromise I am linking for future reference : the people at ACES Central suggest using a .bat file to start Blender with the OCIO variable set only for one application. I will try and see if this allows me to use Redshift with the previous custom OCIO as a system environment variable while keeping the updated OCIO for Blender.
ACES Central: setup Blender using OCIO

Alright, Blender problem solved - kinda. I followed the procedure to install ACES1.2 with a system-wide variable for the OCIO config that replaces the Redshift custom one and the crashes do not happen anymore. From a user point of view, it would be nice if in future versions the issue was met with an **error message** warning about color management issues rather than a crash. On a secondary note the update is now causing issues in Redshift, which _in theory_ should be able to use a separate OCIO config I specified - in practice it seems to have its internal color space categories messed up by the new system environment variable. I will look further into this but I don't think it should be any concern for Blender devs. One possible compromise I am linking for future reference : the people at ACES Central suggest using a .bat file to start Blender with the OCIO variable set only for one application. I will try and see if this allows me to use Redshift with the previous custom OCIO as a system environment variable while keeping the updated OCIO for Blender. [ACES Central: setup Blender using OCIO](https://community.acescentral.com/t/aces-set-up-for-blender-using-ocio/2106/17)

Brecht Van Lommel commented

2023-06-12 15:59:46 +02:00

It indeed should not crash with any OCIO config, at worst give wrong results if the config is incomplete for Blender.

So far I could not reproduce a crash with any of the OCIO configs I have, but that's not too surprising since I have tested those at some point. I guess there is something specific in the Redshift config that is leading to problems.

It indeed should not crash with any OCIO config, at worst give wrong results if the config is incomplete for Blender. So far I could not reproduce a crash with any of the OCIO configs I have, but that's not too surprising since I have tested those at some point. I guess there is something specific in the Redshift config that is leading to problems.

TheArtySquid commented

2023-06-12 16:28:47 +02:00

The Redshift people did confirm on their forum that the RS OCIO is not compatible with Cycles.

I will drop system-wide environment variables for now and take the .bat file approach, supposedly it allows to run multiple OCIO configs on different systems.

The Redshift people did confirm on their forum that the RS OCIO is not compatible with Cycles. I will drop system-wide environment variables for now and take the .bat file approach, supposedly it allows to run multiple OCIO configs on different systems.

Pratik Borhade added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender crashes as soon as an image texture is plugged in the material BSDF node #108868