Blender Crash - Probably node network - probably linked to new hashing code for displacement #54073
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#54073
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
Windows 10 5820K GTX 970
Blender Version
Broken: 2.79 q6968e8-win64
Short description of error
Blender crashes. This can sometimes be whilst editing in the node editor and sometimes whilst rendering. However, the debugger leads me to think it is the same error both times.
I believe it is linked to the new hashing code related to whether displacement needs updating.
I have attached output from Visual Studio in case it is any help.
The crash always seems to be (although clearly not everytime) whilst working out the hash for a FLOAT_ARRAY input to a COLOR_RAMP.
My scene file is quite big and I am struggling to reproduce in a simpler scene. Will keep trying.
Exact steps for others to reproduce the error
It is quite hard to do as sometimes it crashes a few minutes into using node editor and sometimes 20. The same with rendering, sometimes (at the start) of the first frame and sometimes (at the start) of the 30th frame.
Pretty sure it has nothing to do with GPU and rendering as my debug blender is not compiled with CUDA.
Added subscriber: @RevDr
Added subscribers: @brecht, @Sergey
@brecht, not sure this is something to do with the root of this issue, but there are reports of uninitialized memory used in this function
P613: (An Untitled Masterwork)
Worth solving them anyway, could cause some false-positives and considering unchanged graph as changed?
untitled.blend
This issue was referenced by blender/cycles@3eb12a2a2a
This issue was referenced by
b1ee10aa1b
The crash and uninitialized memory were different issues, but both should be fixed now.
Changed status from 'Open' to: 'Resolved'