Geometry Nodes: Crash when enabling "Input Attribute Toggle" on string socket #139
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/test#139
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Original bug report: https://projects.blender.org/blender/blender/issues/157233
System Information
Operating system: Linux-6.14.0-37-generic-x86_64-with-glibc2.39 64 Bits, X11 UI
Graphics card: AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.61, 6.14.0-37-generic) AMD 4.6 (Core Profile) Mesa 25.0.7-0ubuntu0.24.04.2 Opengl Backend
Blender Version
Broken: version: 5.2.0 Alpha, branch: main, commit date: 2026-04-10 23:18, hash:
2229dfdf760cWorked: (newest version of Blender that worked as expected)
Short description of error
Enabling the "Input Attribute Toggle" button on a string socket modifier input crashes.
Exact steps for others to reproduce the error
Report is clear
LLM Reasoning
Got it, let's see. The bug report has a clear title, a short description of the error, and exact steps to reproduce. The steps are numbered, which is good. Even though there's system info, we're ignoring that as per instructions. The description says enabling the toggle on a string socket crashes, and steps show how to do it. So the clarity is there. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 6.397715999999999
}
Report is specific
LLM Reasoning
Got it, let's analyze the bug report. The title is "Geometry Nodes: Crash when enabling 'Input Attribute Toggle' on string socket". The body describes a specific scenario: crashing when enabling that toggle on a string socket in Geometry Nodes. The steps to reproduce are detailed (add geometry nodes modifier, add string input socket, enable the toggle). This is a specific issue because it's about a particular action (enabling Input Attribute Toggle on a string socket) leading to a crash, not a vague "crashing while rendering" or something general. So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 8.179167999999999
}
Report flagged as NOT a duplicate by LLM
Geometry Nodes: Input Attribute Toggle disappears when evaluating closure
https://projects.blender.org/blender/blender/issues/153695
System Information
Operating system: Linux-6.8.0-94-generic-x86_64-with-glibc2.39 64 Bits, X11 UI
Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 580.126.09 Opengl Backend
Blender Version
Broken: version: 5.1.0 Alpha, branch: physics-solver, commit date: 2026-01-30 09:59, hash:
1570c2cf60e3Worked: (newest version of Blender that worked as expected)
Short description of error
Connecting a node group input to an Evaluate Closure node hides the "Input Attribute Toggle" in modifier settings.
Exact steps for others to reproduce the error
The structure type of the socket in the group or Eval Closure node does not matter. I don't see a logical reason why attribute input should be disabled in this case.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1 is about crashing when enabling "Input Attribute Toggle" on a string socket in Geometry Nodes. The steps involve adding a geometry nodes modifier, adding a string input socket, then enabling that toggle—crashes happen here.
Bug report 2 is about the "Input Attribute Toggle" disappearing when connecting to an Evaluate Closure node. The steps are making a geometry nodes modifier, adding a group input (which has the toggle), then connecting to Evaluate Closure, and the toggle disappears.
The key differences: Report 1 is a crash on enabling the toggle for string sockets. Report 2 is the toggle disappearing when connected to Evaluate Closure, regardless of socket type. The issues are different—one is a crash, the other is a UI element disappearing. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.65606,
"duplicate_report_number": "153695"
}
Report flagged as NOT a duplicate by LLM
Geometry Node: Match Node cause crash.
https://projects.blender.org/blender/blender/issues/144362
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce MX450/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99 Opengl Backend
Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-08-10 13:11, hash:
e0170883d428Worked: 4.5
Short description of error
Connect
Resultoutput socket andSwitchinput socket cause crash.Ctrl Shift + Right click on
Resultoutput socket also crash.Exact steps for others to reproduce the error
Resultoutput socket andSwitchinput socket.LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the description and steps for each.
Bug report 1 is about a crash when enabling "Input Attribute Toggle" on a string socket in Geometry Nodes. The steps involve adding a geometry nodes modifier, adding a string input socket, then toggling that attribute button.
Bug report 2 is about a crash when connecting the Result output socket to Switch input socket (or using Ctrl+Shift+Right click on Result) in a Match Node. The steps are opening a specific file and linking those sockets.
The issues are different: one is about a toggle button on a string socket, the other is about connecting specific nodes' sockets. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.080941999999999,
"duplicate_report_number": "144362"
}
Report flagged as NOT a duplicate by LLM
Geometry nodes (Fields) Assertion failed at input_has_attribute_toggle()
https://projects.blender.org/blender/blender/issues/91809
System Information
Operating system: Linux Ubuntu 20.04
Graphics card: Nvidia RTX 3090
Blender Version
Broken: master 4cf4bb2664ebe145dac9715bbbfcc2b96f5ff175 (2021-09-28)
Blender crashes because hitting an assertion:
Exact steps for others to reproduce the error
Stack trace:
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the description and steps to reproduce.
Bug report 1 is about a crash when enabling "Input Attribute Toggle" on a string socket in Geometry Nodes. The steps involve adding a geometry nodes modifier, adding a string input socket, then toggling that attribute button. It mentions it works with Float sockets but crashes with String.
Bug report 2 is about an assertion failure at input_has_attribute_toggle() during certain steps: creating a GN modifier, adding a Math node, connecting Group Input to Math, deselecting, and undo (Ctrl+Z). The crash is due to the assertion in MOD_nodes.cc, specifically related to field_inferencing_interface.
Now, check if they're the same issue. The first report's crash is when toggling the attribute button on a string socket. The second report's crash is during an undo operation involving node connections, leading to the same function (input_has_attribute_toggle) being called with a null interface. But the steps and context are different: one is about enabling the toggle on a string socket, the other is about undo after connecting nodes. So the root cause might be related to input_has_attribute_toggle, but the reproduction steps and scenarios are different. Therefore, they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 32.966657999999995,
"duplicate_report_number": "91809"
}
Report flagged as NOT a duplicate by LLM
GN Tools Crashes - input values modification
https://projects.blender.org/blender/blender/issues/147236
System information
Operating System: Linux 24 LTS
Graphics card: NVIDIA 1070 ti.
Blender Daily from source.
Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-10-05 21:36, hash:
65d5b94740d3Worked: 5.0 froma week or two ago
Short description of error
Blender will crash when running a Geometry node tool from a asset library, and redoing it's action.
Exact steps to reproduce this issue
Toolfrom the top of the 3D viewport.LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the description and steps for each.
Bug Report 1: The issue is about crashing when enabling "Input Attribute Toggle" on a string socket in Geometry Nodes. Steps involve adding a geometry nodes modifier, adding a string input socket, then toggling that button. It mentions it works with float sockets but crashes with string.
Bug Report 2: The issue is Blender crashing when running a Geometry node tool from an asset library and redoing its action (adjusting a value in the redo panel). Steps involve using an asset, running the tool, adjusting a value in redo, then crash.
The key here is the context: one is about a specific UI toggle on a string socket in the modifier, the other is about a tool from an asset library and redo actions. The descriptions and steps are different—different scenarios (modifier input vs. tool from asset) and different triggers (toggle button vs. adjusting value in redo). So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 14.597475999999999,
"duplicate_report_number": "147236"
}
Report flagged as NOT a duplicate by LLM
Crash on adding "Simulation Input"-Node to geometry
https://projects.blender.org/blender/blender/issues/102790
System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48
Blender Version
Broken: version: 3.5.0 Alpha, branch: geometry-nodes-simulation, commit date: 2022-11-24 15:35, hash:
b5ea0d2f41Short description of error
Blender crashes when adding the "Simulation Input"-Node to a geomtry in Geometry Nodes. It works when the "Simulation Output"-Node is added first, but with the Input Node first, it crashes every time.
Exact steps for others to reproduce the error
{F13971604, size=full}
simulation_node_crash.blend
Sorry if this has already been reported but I couldn't find any other report with this problem. Thanks!
LLM Reasoning
Got it, let's analyze the two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1 is about a crash when enabling "Input Attribute Toggle" on a string socket in Geometry Nodes. The steps involve adding a geometry nodes modifier, adding a string input socket, then toggling that attribute button.
Bug report 2 is about a crash when adding a "Simulation Input"-Node to geometry. The steps are opening a .blend file, going to Geometry Nodes, dropping the Simulation Input node after a Curve Circle.
The issues are different: one is about a specific toggle on a string socket in a modifier, the other is about adding a simulation input node. The contexts (modifier vs node addition) and the triggers (toggle button vs node placement) are distinct. So they're not the same issue.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.636356,
"duplicate_report_number": "102790"
}