State:Closed|icon_bug|database:public|icon_mari|Resolution:Fixed|TargetRelease:4.5v2|BugID:378782|
Problem summary
Adding a procedural color layer in a scalar channel causes Mari to crash if there is a custom OCIO config applied.
Customer reported version
4.2v2
Customer reported platform
centos7
Steps to reproduce
1) Open Mari, create a new project and load a custom OCIO config
2) Create a scalar channel from the Channel palette
3) In the Layers palette, create a procedural color layer using the Add Procedural Layer>Basic>Color
4) In the procedural layer's settings open the color picker window to change the color of the layer
Note: In Mari 3.4, choose another color from the color picker window
5) Mari crashes
Workaround
Disabling Color Management fixes the issue.
The crash is not occurring when using one of the following OCIO configs as well: aces, nuke-default, spi-anim, spi-vfx.
Reproduced by support
This bug has been reproduced in:
Mari 4.2v2 - CentOS 7 - Windows 10
Mari 4.2v1 - CentOS 7
Mari 4.1v1 - CentOS 7
Mari 3.4v2 - CentOS 7
Mari 3.4v1 - CentOS 7 - Windows 10 - OSX 10.12.6 - regression
Unable to reproduce bug in:
Mari 4.0v4 - CentOS 7 - Windows 10
Mari 4.0v1 - CentOS 7
Mari 3.3v1 - CentOS 7 - Windows 10 - OSX 10.12.6
Mari 3.2v1 - CentOS 7
Earliest version tested
3.3v1 - This issue no longer appears in this version and has regressed
Expected behaviour
Mari should create a procedural color layer, regardless of the Color Management configurations
Actual behaviour
Mari crashes when creating a procedural color layer
We're sorry to hear that
Please tell us why