Blender crash after math node input socket is removed and switched to another operation #97540

Closed
opened 2022-04-22 08:38:39 +02:00 by Novice · 10 comments

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.50

Blender Version
Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: cc66d1020c
Worked: I don't know.

Short description of error
Blender crash with Error : EXCEPTION_ACCESS_VIOLATION after a math node socket input is removed and then switched to another operation.

Exact steps for others to reproduce the error

  • Open the attached blend file.
  • In python console type
math.inputs.remove(math.inputs['Value'])```
- Change the operation of the Math node from add to Square Root.
![math_from_add_squareroot.JPG](https://archive.blender.org/developer/F13015516/math_from_add_squareroot.JPG)
[crash_after_socket_remove.blend](https://archive.blender.org/developer/F13015512/crash_after_socket_remove.blend)
**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.50 **Blender Version** Broken: version: 3.1.2, branch: master, commit date: 2022-03-31 17:40, hash: `cc66d1020c` Worked: I don't know. **Short description of error** Blender crash with Error : EXCEPTION_ACCESS_VIOLATION after a math node socket input is removed and then switched to another operation. **Exact steps for others to reproduce the error** - Open the attached blend file. - In python console type ```math = D.materials['Material'].node_tree.nodes['Math'] math.inputs.remove(math.inputs['Value'])``` - Change the operation of the Math node from add to Square Root. ![math_from_add_squareroot.JPG](https://archive.blender.org/developer/F13015516/math_from_add_squareroot.JPG) [crash_after_socket_remove.blend](https://archive.blender.org/developer/F13015512/crash_after_socket_remove.blend)
Author

Added subscriber: @BlenderAmateur

Added subscriber: @BlenderAmateur
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Member

Thanks for the report. This isn't a bug though. Blender expects there to be certain sockets on the math node, removing them is not really a supported operation, and there should be no need to do it.
The Python API allows you to create endless situations that break the assumptions of core code since it's mostly a thin wrapper around Blender internals.

Thanks for the report. This isn't a bug though. Blender expects there to be certain sockets on the math node, removing them is not really a supported operation, and there should be no need to do it. The Python API allows you to create endless situations that break the assumptions of core code since it's mostly a thin wrapper around Blender internals.
Author

I never found a reason for doing this. The reason for the report is that it looks like blender crash, and I've been taught that program crashes are a security risk. But perhaps this is a controlled shut down inside blender or the institute have a different design philosophy when coming to security.

Anyway thanks for the quick look at it.

I never found a reason for doing this. The reason for the report is that it looks like blender crash, and I've been taught that program crashes are a security risk. But perhaps this is a controlled shut down inside blender or the institute have a different design philosophy when coming to security. Anyway thanks for the quick look at it.
Member

I get your point. Avoiding crashes with unsupported inputs is nice in principle-- often it leads to performance penalties or increased development time, so there's definitely a balance. The Python API can crash Blender in enough ways that I don't think we can avoid it here.

I get your point. Avoiding crashes with unsupported inputs is nice in principle-- often it leads to performance penalties or increased development time, so there's definitely a balance. The Python API can crash Blender in enough ways that I don't think we can avoid it here.

Added subscriber: @JacobMerrill-1

Added subscriber: @JacobMerrill-1

users can also add subD modifer and set to 8 and crash their whole pc
https://fb.watch/cyLB1zsfEY/

it's up to the user to know a bit about what they are doing also**

users can also add subD modifer and set to 8 and crash their whole pc https://fb.watch/cyLB1zsfEY/ it's up to the user to know a bit about what they are doing also**
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#97540
No description provided.