Dragging in Poly Haven HDRI w/ACES colorspace crashes (viewport render or full render) #115714

New Issue

Ben Jackson · 2023-12-02T22:21:37+01:00

Ben Jackson commented

2023-12-02 22:21:37 +01:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01

Blender Version
Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: d0dd92834a08
Worked: (newest version of Blender that worked as expected)

Short description of error
With OCIO=.../ACES/config.ocio, if you configure an HDRI from Poly Haven by dropping it on the background and then setting the viewport to render, Blender will crash.

Exact steps for others to reproduce the error

Launch Blender with the ACES colorspace config (by setting OCIO or by following tutorials that edit the install files)
Install an asset like abandoned_bakery in your asset library (or get the Poly Haven add-on)
Drag and drop from the asset library to the background.
If needed, set the viewport to rendered mode (if it was initially rendered, Blender already crashed). Blender will crash.

Variations tested:

Does not crash if you simply open the .hdr file from the filesystem (configuring environment texture manually).
Does not crash if you open the asset's .blend file directly.
Does not crash if you drag in the asset (with no rendered 3d viewport visible), save, re-load, and then switch to rendered mode.
Does not crash with default colorspace config.

(Asset-browser ready HDRI attached. I don't see a way to download the .blend file directly from polyhaven.com, only the images)

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01 **Blender Version** Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: `d0dd92834a08` Worked: (newest version of Blender that worked as expected) **Short description of error** With `OCIO=.../ACES/config.ocio`, if you configure an HDRI from Poly Haven by dropping it on the background and then setting the viewport to render, Blender will crash. **Exact steps for others to reproduce the error** 1. Launch Blender with the ACES colorspace config (by setting `OCIO` or by following tutorials that edit the install files) 2. Install an asset like abandoned_bakery in your asset library (or get the Poly Haven add-on) 3. Drag and drop from the asset library to the background. 4. If needed, set the viewport to rendered mode (if it was initially rendered, Blender already crashed). Blender will crash. Variations tested: 1. Does not crash if you simply open the `.hdr` file from the filesystem (configuring environment texture manually). 2. Does not crash if you open the asset's `.blend` file directly. 3. Does not crash if you drag in the asset (with no rendered 3d viewport visible), save, re-load, and then switch to rendered mode. 4. Does not crash with default colorspace config. (Asset-browser ready HDRI attached. I don't see a way to download the `.blend` file directly from polyhaven.com, only the images)

abandoned_bakery.zip

1.8 MiB

Ben Jackson added the

labels 2023-12-02 22:21:38 +01:00

Ben Jackson commented

2023-12-03 03:10:57 +01:00

I just figured out where crash summaries go:

# Blender 4.0.1, Commit date: 2023-11-16 16:40, Hash d0dd92834a08
bpy.context.area.ui_type = 'ASSETS'  # Property
bpy.context.space_data.system_bookmarks_active = 3  # Property
bpy.context.space_data.params.filename = "hdricrash.blend"  # Property
Saved "hdricrash.blend"  # Info

# backtrace
Exception Record:

ExceptionCode         : EXCEPTION_ACCESS_VIOLATION
Exception Address     : 0x00007FF64B805250
Exception Module      : blender.exe
Exception Flags       : 0x00000000
Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000000
	Parameters[1] : 0x0000000000000000


Stack trace:
blender.exe         :0x00007FF64B805250  OCIOImpl::cpuProcessorIsNoOp
blender.exe         :0x00007FF64A981010  IMB_colormanagement_transform
blender.exe         :0x00007FF64A982230  colormanage_imbuf_make_linear
blender.exe         :0x00007FF64A994500  IMB_loadifffile
blender.exe         :0x00007FF64A9946C0  IMB_loadiffname
blender.exe         :0x00007FF64A411FE0  load_image_single
blender.exe         :0x00007FF64A410B00  image_load_image_file
blender.exe         :0x00007FF64A40FB20  image_acquire_ibuf
blender.exe         :0x00007FF64A413500  BKE_image_acquire_ibuf
blender.exe         :0x00007FF64A5DCF60  image_get_gpu_texture
blender.exe         :0x00007FF64A8851A0  DRW_shgroup_add_material_resources
blender.exe         :0x00007FF64A8864E0  DRW_shgroup_material_create
blender.exe         :0x00007FF64A891D80  EEVEE_lightprobes_cache_init
blender.exe         :0x00007FF64A8989F0  eevee_cache_init
blender.exe         :0x00007FF64A86BBF0  drw_engines_cache_init
blender.exe         :0x00007FF64A86E270  DRW_draw_render_loop_ex
blender.exe         :0x00007FF64A86F640  DRW_draw_view
blender.exe         :0x00007FF64B3C69F0  view3d_main_region_draw
blender.exe         :0x00007FF64ABA9AF0  ED_region_do_draw
blender.exe         :0x00007FF64A74C7A0  wm_draw_window_offscreen
blender.exe         :0x00007FF64A74C5D0  wm_draw_window
blender.exe         :0x00007FF64A74C000  wm_draw_update
blender.exe         :0x00007FF64A71B350  WM_main
blender.exe         :0x00007FF64A17A9B0  main
blender.exe         :0x00007FF64E9137D4  __scrt_common_main_seh
KERNEL32.DLL        :0x00007FFE36DD2560  BaseThreadInitThunk
ntdll.dll           :0x00007FFE3846AA30  RtlUserThreadStart

I just figured out where crash summaries go: ``` # Blender 4.0.1, Commit date: 2023-11-16 16:40, Hash d0dd92834a08 bpy.context.area.ui_type = 'ASSETS' # Property bpy.context.space_data.system_bookmarks_active = 3 # Property bpy.context.space_data.params.filename = "hdricrash.blend" # Property Saved "hdricrash.blend" # Info # backtrace Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FF64B805250 Exception Module : blender.exe Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0x0000000000000000 Stack trace: blender.exe :0x00007FF64B805250 OCIOImpl::cpuProcessorIsNoOp blender.exe :0x00007FF64A981010 IMB_colormanagement_transform blender.exe :0x00007FF64A982230 colormanage_imbuf_make_linear blender.exe :0x00007FF64A994500 IMB_loadifffile blender.exe :0x00007FF64A9946C0 IMB_loadiffname blender.exe :0x00007FF64A411FE0 load_image_single blender.exe :0x00007FF64A410B00 image_load_image_file blender.exe :0x00007FF64A40FB20 image_acquire_ibuf blender.exe :0x00007FF64A413500 BKE_image_acquire_ibuf blender.exe :0x00007FF64A5DCF60 image_get_gpu_texture blender.exe :0x00007FF64A8851A0 DRW_shgroup_add_material_resources blender.exe :0x00007FF64A8864E0 DRW_shgroup_material_create blender.exe :0x00007FF64A891D80 EEVEE_lightprobes_cache_init blender.exe :0x00007FF64A8989F0 eevee_cache_init blender.exe :0x00007FF64A86BBF0 drw_engines_cache_init blender.exe :0x00007FF64A86E270 DRW_draw_render_loop_ex blender.exe :0x00007FF64A86F640 DRW_draw_view blender.exe :0x00007FF64B3C69F0 view3d_main_region_draw blender.exe :0x00007FF64ABA9AF0 ED_region_do_draw blender.exe :0x00007FF64A74C7A0 wm_draw_window_offscreen blender.exe :0x00007FF64A74C5D0 wm_draw_window blender.exe :0x00007FF64A74C000 wm_draw_update blender.exe :0x00007FF64A71B350 WM_main blender.exe :0x00007FF64A17A9B0 main blender.exe :0x00007FF64E9137D4 __scrt_common_main_seh KERNEL32.DLL :0x00007FFE36DD2560 BaseThreadInitThunk ntdll.dll :0x00007FFE3846AA30 RtlUserThreadStart ```

Philipp Oeser commented

2023-12-05 10:00:11 +01:00

Launch Blender with the ACES colorspace config (by setting OCIO or by following tutorials that edit the install files)

What is the ACES colorspace config (seems there are multiple)?
Could you be specific where you got this and how exactly you set it up?

> Launch Blender with the ACES colorspace config (by setting OCIO or by following tutorials that edit the install files) What is `the ACES colorspace config` (seems there are multiple)? Could you be specific where you got this and how exactly you set it up?

Ben Jackson commented

2023-12-06 05:17:58 +01:00

I downloaded it from https://github.com/colour-science/OpenColorIO-Configs/tree/feature/aces-1.2-config and specifically I used the aces_1.2 folder.

Many tutorials advise you to replace the blender colorspace directory but that isn't necessary. OCIO will look for the OCIO environment variable. I launched Blender like this:

set OCIO=C:\Users\benja\Projects\Blender\ACES\config.ocio
blender.exe

That ACES dir is the exact contents of aces_1.2 from the repo above.

I suspect the only thing that's important here is that all of the default colorspaces are removed, so the attempt to use an asset with a texture with a missing colorspace results in a crash. Something sanitizes that missing colorspace in other circumstances (like when loading a .blend file).

I downloaded it from https://github.com/colour-science/OpenColorIO-Configs/tree/feature/aces-1.2-config and specifically I used the aces_1.2 folder. Many tutorials advise you to replace the blender `colorspace` directory but that isn't necessary. OCIO will look for the `OCIO` environment variable. I launched Blender like this: ``` set OCIO=C:\Users\benja\Projects\Blender\ACES\config.ocio blender.exe ``` That `ACES` dir is the exact contents of `aces_1.2` from the repo above. I suspect the only thing that's important here is that all of the default colorspaces are removed, so the attempt to use an asset with a texture with a missing colorspace results in a crash. Something sanitizes that missing colorspace in other circumstances (like when loading a `.blend` file).

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

Dragging in Poly Haven HDRI w/ACES colorspace crashes (viewport render or full render) #115714