Mesh Boolean node crash when operation is keyframed #110562
Labels
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#110562
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?
System Information
Operating system: Windows-11-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67
Blender Version
Broken: version: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-28 00:04, hash:
9a37a206cf5c
Worked: didn't test
Mesh Boolean node crash when operation is keyframed
Exact steps for others to reproduce the error
Difference
)Union
Original report
Open the .blend and go to frame 60. Crash
Exact steps for others to reproduce the error
This is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.
It just said: "Code marked as unreachable has been executed. Please report this as a bug."
Apologies for the low quality report.
Hi, can you attach
C:\Users\RAIMUN~1.KLI\AppData\Local\Temp\untitled.crash.txt
too?Can redo the crash in current master:
Still crashing with latest master
Blender Crash. Code marked as unreachable has been executed.to Crash: Code marked as unreachable has been executed.Seem to be caused by the
Mesh Boolean
nodeoperation
being animatedIf I remove the animation, I dont get it to crash
Crash: Code marked as unreachable has been executed.to Mesh Boolean node crash when operation is keyframedWill raise the priority here since this is a crasher (that is not totally uncommon to run into)
This is an interesting issue! An important one too. The problem is that the boolean operation changes which sockets are available, and the availability is used during evaluation to change which values are computed. Normally the availability changes are followed by
rna_NodeSocket_update
. For various reasons though, the animation system cannot call RNA property's update functions. This leaves two options:-- These updates before evaluation couldn't deal with properties that cause changes in the node group interface and potential dependencies between node groups. That's one important limitation.
-- Since the RNA "set" functions are called from multiple threads, the update tagging would have to be made atomic.
Of those, I think option 1 is much safer and better for the long term sanity of this area. But I'm worried about how many people might be depending on animation of these node properties right now.
Thank you, Hans! <3