Geometry Nodes related memory leak and exception access violation #109219
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109219
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-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98
Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash:
e1ccd9d4a1d3Worked:
Short description of error
Blender freezes, memory usage spikes and eventually you get exception access violation crash.
Exact steps for others to reproduce the error
Open attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.
gnodes bug1.blend
To stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the "fir_twig" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.
Hi, thanks for the report.
I can even redo the crash when noddle is removed.
yeah, removing it from object info node aviods the crash.
In debug build I noticed some warning/messages to change data type to int64_t
Maybe this is relevant to the issue?
Geometry nodes is not supporting
int64_tright now. So, this just extremely high mesh for geometry nodes right now.I'll close this as precision/supported data size issues are not bugs.
See https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook.
You are missing the bug! The
fir_twigobject was deleted and is not selected in the group input, there is only a 'ghost' reference to it in the object input node itself.fir_twigobject should be ignored from the geometry calc. Please re-open this bug report.The only thing I see here is that we should not create dependencies for busy sockets. That is, if you connect a link, the modifier must not create a dependency on that socket.
But otherwise, everything works correctly. Here is a graph where your node causes your giant object to be evaluated, which is not supported:
I think I understand what you are saying. This definitely caught me by surprise as I would not expect for this to have any effect on performance (and it should not like you said), since the geometry link is disconnected. The size of the object suddenly increased when I changed some of the geometry nodes logic, so I deleted it, but it looks like it was not gone even after trying to run clean up operations.
I am sure a lot of people are experiencing geometry nodes performance lag without even realizing that a remaining reference to an object someplace is causing it.
@ValBarashkov This is a known limitation, we cannot predict that sockets and their data are not being used based on a node tree evaluation. But disabling for connected links makes sense.
thanks @mod_moder , re-confirming.