Geometry Node: Memory leak -> EXCEPTION_ACCESS_VIOLATION -> EXCEPTION_INT_DIVIDE_BY_ZERO. #102238
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#102238
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.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15
Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-10-03 00:19, hash:
d4d40f3b69Short description of error
acf083a5bfand previous0a852884620348bc88e4and nextIn recent versions, it all depends on whether the attempt to free memory will be in the available area (overflowed int megabytes freed?) or in the system area (deny access) or division by 0 (size of freed memory)
Message in the console after crashing
1:
Error: Not freed memory blocks: 2, total unfreed memory 0.000015 MB
2:
Error: Not freed memory blocks: 4294967293, total unfreed memory 0.000000 MB
3:
Error : EXCEPTION_ACCESS_VIOLATION
User message:
Error : EXCEPTION_INT_DIVIDE_BY_ZERO
Exact steps for others to reproduce the error
In the attached .blend
bug.blend
On the default cube
crash_example.mkv
Added subscriber: @DanielJH
Added subscriber: @mod_moder
Thanks for the report. I can confirm. But the problem is, based on my investigation, I need to edit your report a bit. This will be information about how this bug changed.
Thanks, feel free to edit in more info/corrections, that was just my best guess based on how I was able to reproduce it.
Div by zero crash on geometry nodetrees that produce empty geometry with output attributes.to Geometry Node: Memory leak -> EXCEPTION_ACCESS_VIOLATION -> EXCEPTION_INT_DIVIDE_BY_ZERO.Changed status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @HooglyBoogly, @JacquesLucke
@HooglyBoogly Currently it is not very well defined whether
customData_add_layer__internaltakes ownership of thelayerdataor not. Especially whentotelem == 0it's tricky, because the function just frees the pointer which is not possible to detect from the outside. Do you have an idea for how the situation could be improved? We could pass invoid **layerdata, then the caller could check whether that has been set to null, indicating that the function took ownership.Hmm, I'm not sure I agree. With
CD_ASSIGN, the function takes ownership of the array. For all other modes, no ownership is transferred.I think that's relatively straightforward, but I didn't look into this bug specifically yet so I don't know the full problem.
Not quite true, the function has an early return. If the function always takes ownership then the
MEM_freeNin theMoveArraycase inadd_builtin_type_custom_data_layer_from_initdoes not make sense.Okay, I see. Anyway, that's the design we should move to I think.
This issue was referenced by
e031a45d60Changed status from 'Confirmed' to: 'Resolved'