Page MenuHome

crash on color managment setting
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14802 Core Profile Context 21.10.2 30.0.14005.1000

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2021-11-30 21:25, hash: rB88e9e97ee907
Worked: (newest version of Blender that worked as expected)

Short description of error
Changing look to medium/high contrast causes crash of program

Exact steps for others to reproduce the error
Material preview/rendered view> color management>look>high contrast/medium contrast

Event Timeline

Jesse Yurkovich (deadpin) changed the task status from Needs Triage to Needs Information from User.Dec 2 2021, 6:00 AM

I'm not able to reproduce this crash on AMD or nVidia here (in case it mattered). Please follow the below instructions to troubleshoot and provide the additional log files.


Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to reproduce the error again. Once it crashes or you close Blender manually the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

i am unable to find blender 3.1's download path
however when blender 'crashes' it appears that the program has just been closed

You can still check for that crash file in your temp directory at least. How did you install blender? With the MSI, Steam, or Windows Store?

I installed through amd's website
I will looks some more for any crash files

Jesse Yurkovich (deadpin) changed the task status from Needs Information from User to Needs Triage.Dec 3 2021, 3:08 AM

Setting back to Needs Triage to see if someone else might be able to investigate. Will move the crash file into the description on my next edit.

OpenColorIO_v2_0::Context::resolveFileLocation
OpenColorIO_v2_0::Context::resolveFileLocation
OpenColorIO_v2_0::BuildFileTransformOps

Hi, may be you are using OCIO v2?


Note: this is not intended to be a complete production-ready config: https://opencolorio.readthedocs.io/en/latest/configurations/ocio_v2_demo.html:
Considering the note, I think crash like this are expected. no?

I have seen similar reports recently on tracker but couldn't find at the moment (will check again)

edit: Found them: T93562, T93828

@ryan (cxril) I took another look at this and it seems like you are running blender from the following path: C:\Users\ryan\AppData\Local\Temp\Rar$EXa3988.34656\blender-3.1.0-alpha+master.88e9e97ee907-windows.amd64-release

It turns out OCIO has a feature that attempts to resolve variables inside the path and it uses $ as the marker for such variables[1]. Can you try running blender from a more "normal" path and see if you can still reproduce the problem?

[1] OCIO Documentation

Jesse Yurkovich (deadpin) changed the task status from Needs Triage to Needs Information from User.Dec 24 2021, 3:56 AM

I couldn't find anything under that directory, I will continue to search for the file as I installed blender 3.1 through AMD's website.

Hi, may be you are using OCIO v2?

Blender was upgraded to OCIO_v2 in February.
T84819: OpenColorIO 2.0 Upgrade


Note: this is not intended to be a complete production-ready config: https://opencolorio.readthedocs.io/en/latest/configurations/ocio_v2_demo.html:
Considering the note, I think crash like this are expected. no?

The full sentence states it’s purpose. 😉

Note: this is not intended to be a complete production-ready config, its purpose is to introduce many of the new features in OCIO v2.

It is a highly documented config aimed at developers, designed to help them implement OCIO_v2 in their apps. If it crashes the application, then I would think that something is wrong in that app’s implementation/code. That demo config is designed to teach, not to be a production ready solution. 😊

I will close this issue for now. If you can reproduce the problem in the future, please open a new report.