Color management Display Device other than sRGB segfaults Blender #58816

New Issue

CansecoGPC · 2018-12-05T20:16:45+01:00

CansecoGPC commented

2018-12-05 20:16:45 +01:00

System Information
Operating system: GNU/Linux Manjaro KDE
Graphics card: NVIDIA GTX 750 Ti

Blender Version
Broken:
Blender 2.80, 9b228e465f, 2018-12-05

Short description of error

On Color management, Display Device, selecting any option except sRGB makes Blender 2.80 Beta (9b228e465f) segfault with: OpenColorIO Error: DisplayTransform error. Cannot find display colorspace, ''.

Exact steps for others to reproduce the error
Open Blender, go to Render tab, Color Management, Display Device, select anything except sRGB.
Happens the same when opening files with a different Display Device selected.

**System Information** Operating system: GNU/Linux Manjaro KDE Graphics card: NVIDIA GTX 750 Ti **Blender Version** Broken: Blender 2.80, 9b228e465f13, 2018-12-05 **Short description of error** On Color management, Display Device, selecting any option except sRGB makes Blender 2.80 Beta (9b228e465f13) segfault with: OpenColorIO Error: DisplayTransform error. Cannot find display colorspace, ''. **Exact steps for others to reproduce the error** Open Blender, go to Render tab, Color Management, Display Device, select anything except sRGB. Happens the same when opening files with a different Display Device selected.

CansecoGPC commented

2018-12-05 20:16:45 +01:00

Added subscriber: @CansecoGPC

Philipp Oeser commented

2018-12-06 09:24:53 +01:00

Added subscribers: @Sergey, @lichtwerk

Sergey Sharybin was assigned by Philipp Oeser

2018-12-06 09:24:53 +01:00

Philipp Oeser commented

2018-12-06 09:24:53 +01:00

Confirmed.

in create_display_buffer_processor()
OCIO_ConstConfigRcPtr *config = OCIO_getCurrentConfig()
config seems to be garbled, following then leads to OCIO_abort()

1   raise                                                                     0x7ffff466a53f 
2   abort                                                                     0x7ffff4654895 
3   OCIO_reportError                               ocio_impl.cc          74   0x6251c18      
4   OCIO_reportException                           ocio_impl.cc          79   0x6251c43      
5   OCIOImpl::configGetProcessor                   ocio_impl.cc          467  0x625303f      
6   OCIO_configGetProcessor                        ocio_capi.cc          187  0x624ece2      
7   create_display_buffer_processor                colormanagement.c     826  0x2e51e63      
8   update_glsl_display_processor                  colormanagement.c     3405 0x2e57012      
9   IMB_colormanagement_setup_glsl_draw_from_space colormanagement.c     3453 0x2e570d3      
10  DRW_transform_to_display                       draw_manager.c        274  0x27fd3fc      
11  workspace_aa_draw_transform                    workbench_effect_aa.c 67   0x28858b2      
12  workbench_aa_draw_pass                         workbench_effect_aa.c 95   0x2885a89      
13  workbench_deferred_draw_scene                  workbench_deferred.c  1081 0x2885649      
14  workbench_solid_draw_background                solid_mode.c          68   0x2849549      
15  drw_engines_draw_background                    draw_manager.c        1038 0x27ff230      
16  DRW_draw_render_loop_ex                        draw_manager.c        1492 0x2800363      
17  DRW_draw_view                                  draw_manager.c        1395 0x27ffef7      
18  view3d_draw_view                               view3d_draw.c         1319 0x1da1e8e      
19  view3d_main_region_draw                        view3d_draw.c         1340 0x1da1f3e      
20  ED_region_do_draw                              area.c                529  0x22206b1

@Sergey: mind checking again?

Confirmed. in `create_display_buffer_processor()` OCIO_ConstConfigRcPtr *config = OCIO_getCurrentConfig() `config` seems to be garbled, following then leads to OCIO_abort() ``` 1 raise 0x7ffff466a53f 2 abort 0x7ffff4654895 3 OCIO_reportError ocio_impl.cc 74 0x6251c18 4 OCIO_reportException ocio_impl.cc 79 0x6251c43 5 OCIOImpl::configGetProcessor ocio_impl.cc 467 0x625303f 6 OCIO_configGetProcessor ocio_capi.cc 187 0x624ece2 7 create_display_buffer_processor colormanagement.c 826 0x2e51e63 8 update_glsl_display_processor colormanagement.c 3405 0x2e57012 9 IMB_colormanagement_setup_glsl_draw_from_space colormanagement.c 3453 0x2e570d3 10 DRW_transform_to_display draw_manager.c 274 0x27fd3fc 11 workspace_aa_draw_transform workbench_effect_aa.c 67 0x28858b2 12 workbench_aa_draw_pass workbench_effect_aa.c 95 0x2885a89 13 workbench_deferred_draw_scene workbench_deferred.c 1081 0x2885649 14 workbench_solid_draw_background solid_mode.c 68 0x2849549 15 drw_engines_draw_background draw_manager.c 1038 0x27ff230 16 DRW_draw_render_loop_ex draw_manager.c 1492 0x2800363 17 DRW_draw_view draw_manager.c 1395 0x27ffef7 18 view3d_draw_view view3d_draw.c 1319 0x1da1e8e 19 view3d_main_region_draw view3d_draw.c 1340 0x1da1f3e 20 ED_region_do_draw area.c 529 0x22206b1 ``` @Sergey: mind checking again?

Philipp Oeser commented

2018-12-06 09:29:14 +01:00

still get it after a60536956e

still get it after a60536956e

Rainer Trummer commented

2018-12-06 09:37:37 +01:00

Added subscriber: @RainerTrummer

Rainer Trummer commented

2018-12-06 09:40:30 +01:00

Same thing here on Windows. This started yesterday at some point, another compiled version with hash 245065460f works just fine. If the user has set that color space in his startup file (like I did), Blender never starts and throws the 'Cannot find Colorspace' Error on startup.

Same thing here on Windows. This started yesterday at some point, another compiled version with hash 245065460f3 works just fine. If the user has set that color space in his startup file (like I did), Blender never starts and throws the 'Cannot find Colorspace' Error on startup.

blender-admin commented

2018-12-06 10:55:31 +01:00

This issue was referenced by 0e5f97a3a1

This issue was referenced by 0e5f97a3a1b3ad2bc49b2e553345bd191b2e06cf

Sergey Sharybin commented

2018-12-06 11:03:42 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2018-12-06 11:03:42 +01:00

CansecoGPC commented

2018-12-06 12:33:40 +01:00

I can confirm that the bug has been fixed, thanks, and keep up the good work.