Colormanagement leads to crash with python #32803
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#32803
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
%%%Install the attached Addon, switch to the Video Editing screen layout, replace the curve editor by a File browser, select a video file and klick the Edit Range button in the Movie Manager section in the Sequencer's property panel.
Blender Crashes without returning a python realted error. gdb output is:
Program received signal SIGSEGV, Segmentation fault.
0x000000000208ade9 in IMB_colormanagement_assign_float_colorspace (ibuf=0x77b0838, name=0x774a2f0 "")
1086 if (colorspace->is_data)
%%%
Changed status to: 'Open'
%%%I tried this in rev 51152 but couldnt redo crash (64bit linux)
could you see if this bug still happens in a recent revision?%%%
%%%Campbell, yes the crash is still happens here. Looking into this.%%%
%%%Issue was caused by wrong sequencer color space set for new scenes. Fixed in svn rev51168, thanks for the report, closing.%%%
Changed status from 'Open' to: 'Resolved'