output_node.inputs.new() crash blender #103824
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#103824
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
System Information
Operating system: Linux-5.15.0-57-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01
Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash:
55485cb379
Worked: (newest version of Blender that worked as expected)
Short description of error
input = output_node.inputs.new(type = 'RGBA',name = 'bob_sfog',identifier='bob_sfog')
crash blender
Exact steps for others to reproduce the error
Open blender
execute line by line this srcript:
Added subscriber: @barakooda
output_node.inputs.new crash blenderto output_node.inputs.new() crash blenderChanged status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @lichtwerk
Think adding inputs to such node is not really expected to work, the crash is a regression though, checking...
Not sure what you mean.
Output node support multi inputs either outputing to multi layer exr or multi files.
The ui support it.
How will you add inputs then in proper
Python way ? (Not realying on context)
Added subscriber: @mod_moder
This issue was covered in another meeting report. You can't just create a socket. Node must have a method to do this, or you're just breaking it (#103150 (Runtime error on trying to create new input/output to node groups via python)).
Hard to bisect (since in a lite build it would still crash, even if it created the socket, shortly after), in an case, behavior changed between
b9123b806f
(good) ande2e4c1daaa
(bad)In any case, the "proper" way to do it would probably be to use these two (instead of
node.inputs.new()
/node.inputs.clear()
):Changed status from 'Confirmed' to: 'Needs User Info'
Hold on, you dont even need to use the operator, this is exposed in the API like this
@barakooda : does this work for you?
I think crash needs to be investigated as a problem in itself.
Hi philip,
Thank you for the update,
Sorry but i dont see how using the
"ops" is a proper pythonic way.
Programing wise, we prefer to use objects, manipulate data directly and not thru context manager.
For some cases the "ops" is source of all evil when you have a large code base.
The performance hit in some cases can be huge.
Please, hear our pain 💔,
Keep up the great work !
Thank you !
Will check next week.
Thank you.
Thanks @lichtwerk
Its works.
Off topic of this thread.
for the multi channel EXR file case it will be good to add this inputs types:
UINT32 : 1 channel,2 channel,rgb,rgba
HALF-FLOAT :1 channel,2 channel,rgb,rgba
FLOAT : 1 channel,2 channel,rgb,rgba
Then,
I think we it will be good start to utilize the EXR container as it meant to be used.
will link this comment in relevant thread.
Thanks again.
@lichtwerk , think this should not crash even though API is used incorrectly.
Should we track this crash report considering it's a regression?
I would think so, yes.
OK, seems #108728 is the way to go
since dynamic declarations seemed a bit more involved, I still made a PR that gets rid of the crash, see !118807