Segfault in src/blender/imbuf/intern/colormanagement.c, line 650 (config = OCIO_configCreateFromFile(configfile)) in colormanagement_init on Debian jessie #39560

Closed
opened 2014-04-02 11:01:36 +02:00 by Valentin · 12 comments

System Information
Debian jessie/sid, Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)

Blender Version
Broken: own build, Date: 2014-04-01 17:17, Hash: bfe29e0, Branch master
Worked: In all the official Blender bundles I had before

Short description of error
After starting blender in command line nothing happens and I get the message "Speicherzugriffsfehler" (engl. segmentation fault"), without any stacktrace. I tried around and found out that it fails in src/blender/imbuf/intern/colormanagement.c, line 650, which is »config = OCIO_configCreateFromFile(configfile)«. After commenting it out Blender starts.
I used CMake for the build.
gcc Version: gcc (Debian 4.8.2-16) 4.8.2
git log: commit eed3974d11
opencolorio: version 1.0.8

**System Information** Debian jessie/sid, Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) **Blender Version** Broken: own build, Date: 2014-04-01 17:17, Hash: bfe29e0, Branch master Worked: In all the official Blender bundles I had before **Short description of error** After starting blender in command line nothing happens and I get the message "Speicherzugriffsfehler" (engl. segmentation fault"), without any stacktrace. I tried around and found out that it fails in src/blender/imbuf/intern/colormanagement.c, line 650, which is »config = OCIO_configCreateFromFile(configfile)«. After commenting it out Blender starts. I used CMake for the build. gcc Version: gcc (Debian 4.8.2-16) 4.8.2 git log: commit eed3974d11af6072174a43f6b103c9b64be054e2 opencolorio: version 1.0.8
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @blenderscripter

Added subscriber: @blenderscripter

Added subscriber: @Sergey

Added subscriber: @Sergey

Am i right it only happens with your own builds? If so, please provide full backtrace of the crash. Also, which OCIO library you're using?

Am i right it only happens with your own builds? If so, please provide full backtrace of the crash. Also, which OCIO library you're using?
Author

Yes, it happens only with my own builds. I can't find any backtrace, there's nothing in the console and no file in /tmp. Is there another place I should search for it? I use libopencolorio and libopencolorio-dev from the official jessie packages. Hope I could help

Yes, it happens only with my own builds. I can't find any backtrace, there's nothing in the console and no file in /tmp. Is there another place I should search for it? I use libopencolorio and libopencolorio-dev from the official jessie packages. Hope I could help

To get a backtrace, compile in debug mode, then:

$ gdb ./blender # from whetever your build binary is, this will start gdb's console

run
thread apply all bt

Store the backtrace to the file and attach it here. That would help a bunch.

To get a backtrace, compile in debug mode, then: $ gdb ./blender # from whetever your build binary is, this will start gdb's console > run > thread apply all bt Store the backtrace to the file and attach it here. That would help a bunch.
Author

Good to know. Here is the backtrace. backtrace.txt

Good to know. Here is the backtrace. [backtrace.txt](https://archive.blender.org/developer/F83875/backtrace.txt)

Added subscriber: @mont29

Added subscriber: @mont29

What's strange in the backtrace is that there's a jump from libyaml-0.3 to libyaml-0.5. This might me caused by the way how debian packages are build -- they might not all be updated to use latest yaml library which would give issues if application uses mix of this libs.

Saied that, we've got special workaround in our install_deps.sh to make sure proper yaml is used on ubuntu.

Think @mont29 might give more info here, he was investigating the issue. But currently it seems the only way for you is to use ow OCIO library to be sure it's linked against proper yaml library.

What's strange in the backtrace is that there's a jump from libyaml-0.3 to libyaml-0.5. This might me caused by the way how debian packages are build -- they might not all be updated to use latest yaml library which would give issues if application uses mix of this libs. Saied that, we've got special workaround in our install_deps.sh to make sure proper yaml is used on ubuntu. Think @mont29 might give more info here, he was investigating the issue. But currently it seems the only way for you is to use ow OCIO library to be sure it's linked against proper yaml library.
Author

For trying around with coding Blender I can simple outcomment the line and it works for me :-). It should only work right in the official release

For trying around with coding Blender I can simple outcomment the line and it works for me :-). It should only work right in the official release

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-04-04 22:43:11 +02:00

What can I say, except quoting the warning I put in install_deps.sh init message?

WARNING! Ubuntu users: Beware of Trusty!!!
Ubuntu 14.4 comes with a default libyaml-cpp in 0.5 version, while their ocio package still uses the 0.3 version
You have to use '--libyaml-cpp-ver=0.3' option (else Blender will builds with 0.5, and break when using packaged ocio)...

Unfortunately, looks like Debian testing/unstable now has the same issue, so you have to re-run install_deps script with this parameter…

Not a Blender bug at all, thanks for the report anyway.

What can I say, except quoting the warning I put in install_deps.sh init message? > WARNING! Ubuntu users: Beware of Trusty!!! > Ubuntu 14.4 comes with a default libyaml-cpp in 0.5 version, while their ocio package still uses the 0.3 version > You have to use '--libyaml-cpp-ver=0.3' option (else Blender will builds with 0.5, and break when using packaged ocio)... Unfortunately, looks like Debian testing/unstable now has the same issue, so you have to re-run install_deps script with this parameter… Not a Blender bug at all, thanks for the report anyway.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#39560
No description provided.