Geometry Nodes: Crash when enabling "Input Attribute Toggle" on string socket #52

New Issue

Open

opened 2026-04-12 17:52:36 +00:00 by Triager-bot · 7 comments

Triager-bot commented 2026-04-12 17:52:36 +00:00

Owner

Copy Link

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: 2229dfdf760c
Worked: (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

1. Add geometry nodes modifier.
2. Add input socket of type String.
3. Enable the "Input Attribute Toggle" button next to the input value in the modifier UI. Doesn't matter if the socket is unused and grayed out, crashes either way. It works fine with Float type sockets.
   

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: `2229dfdf760c` Worked: (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** 1. Add geometry nodes modifier. 2. Add input socket of type String. 3. Enable the "Input Attribute Toggle" button next to the input value in the modifier UI. Doesn't matter if the socket is unused and grayed out, crashes either way. It works fine with Float type sockets. <img width="276" alt="image.png" src="attachments/4f17698c-93c1-45b3-bf5f-d09aa6d36b9c">

image.png

15 KiB

Triager-bot added the

Status

Needs review

label 2026-04-12 17:52:36 +00:00

Triager-bot commented 2026-04-12 17:52:45 +00:00

Author

Owner

Copy Link

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.461408
}

<!-- ID: CLARITY_CHECK --> ### Report is clear <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 6.461408 } </details>

👍 1

Triager-bot commented 2026-04-12 17:52:54 +00:00

Author

Owner

Copy Link

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.204231
}

<!-- ID: SPECIFIC_REPORT --> ### Report is specific <details> <summary>LLM Reasoning</summary> 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'. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 8.204231 } </details>

👍 1

Triager-bot commented 2026-04-12 17:53:08 +00:00

Author

Owner

Copy Link

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: 1570c2cf60e3
Worked: (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

1. Make a geometry nodes modifier
2. Add a group input socket (shows the attribute toggle)
3. Connect the input socket to an Evaluate Closure node inside the group. The attribute toggle disappears.

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.636832,
"duplicate_report_number": "153695"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Geometry Nodes: Input Attribute Toggle disappears when evaluating closure</summary> 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: `1570c2cf60e3` Worked: (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** 1. Make a geometry nodes modifier 2. Add a group input socket (shows the attribute toggle) 3. Connect the input socket to an _Evaluate Closure_ node inside the group. The attribute toggle disappears. 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. </details> <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 13.636832, "duplicate_report_number": "153695" } </details>

👍 1

Triager-bot commented 2026-04-12 17:53:21 +00:00

Author

Owner

Copy Link

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: e0170883d428
Worked: 4.5

Short description of error
Connect Result output socket and Switch input socket cause crash.
Ctrl Shift + Right click on Result output socket also crash.

Exact steps for others to reproduce the error

1. Open Match String node crash.
2. linked Result output socket and Switch input 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.202322,
"duplicate_report_number": "144362"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Geometry Node: Match Node cause crash.</summary> 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: `e0170883d428` Worked: 4.5 **Short description of error** Connect `Result` output socket and `Switch` input socket cause crash. Ctrl Shift + Right click on `Result` output socket also crash.  **Exact steps for others to reproduce the error** 1. Open [Match String node crash](/attachments/88f16e71-6f99-4861-a870-ee77e53ab5d5). 2. linked `Result` output socket and `Switch` input socket. </details> <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.202322, "duplicate_report_number": "144362" } </details>

👍 1

Triager-bot commented 2026-04-12 17:53:54 +00:00

Author

Owner

Copy Link

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:

BLI_assert failed: source/blender/modifiers/intern/MOD_nodes.cc:320, input_has_attribute_toggle(), at 'node_tree.field_inferencing_interface != nullptr'

Exact steps for others to reproduce the error

1. Start blender
2. Enter geometry nodes workspace
3. Click New to create a new GN modifier
4. Add a new Math node
5. Connect a new output socket from Group Input into the first socket of the Math node
6. Click on empty space to deselect nodes
7. Hit Ctrl+Z
8. Crash

Stack trace:

- 0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
- 1  0x00007ffff6dd2859 in __GI_abort () at abort.c:79
- 2  0x000000001aff98ae in _BLI_assert_abort () at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/BLI_assert.c:61
- 3  0x000000000631e3f2 in input_has_attribute_toggle(bNodeTree const&, int) (node_tree=..., socket_index=1)
    at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:320
#4  0x0000000006325d2b in initialize_group_input(NodesModifierData&, blender::nodes::OutputSocketRef const&, void*)
    (nmd=..., socket=..., r_value=0x60e000097498) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:693
#5  0x000000000632b95d in compute_geometry(blender::nodes::DerivedNodeTree const&, blender::Span<blender::nodes::NodeRef const*>, blender::nodes::NodeRef const&, GeometrySet, NodesModifierData*, ModifierEvalContext const*)
    (tree=..., group_input_nodes=..., output_node=..., input_geometry_set=..., nmd=0x60f000191cb8, ctx=0x7fffbc7a0bd0)
    at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:934
#6  0x000000000632de20 in modifyGeometry(ModifierData*, ModifierEvalContext const*, GeometrySet&)
    (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=...)
    at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1066
#7  0x000000000632e768 in modifyGeometrySet(ModifierData*, ModifierEvalContext const*, GeometrySet*)
    (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=0x7fffbc7a0ed0)
    at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1093
#8  0x0000000004902d86 in modifier_modify_mesh_and_geometry_set(ModifierData*, ModifierEvalContext const&, Mesh*, GeometrySet&)
    (md=0x60f000191cb8, mectx=..., input_mesh=0x61c00011f088, geometry_set=...)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:953
#9  0x00000000049067df in mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)
    (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, use_deform=true, need_mapping=false, dataMask=0x7fffbc7a15a0, index=-1, use_cache=true, allow_shared_mesh=true, r_deform=0x7fffbc7a14a0, r_final=0x7fffbc7a1480, r_geometry_set=0x7fffbc7a14c0)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1291
#10 0x000000000490da2b in mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool)
    (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, dataMask=0x7fffbc7a15a0, need_mapping=false)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1914
#11 0x000000000490f684 in makeDerivedMesh(Depsgraph*, Scene*, Object*, BMEditMesh*, CustomData_MeshMasks const*)
    (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, em=0x0, dataMask=0x7fffbc7a16c0)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:2061
#12 0x00000000037cee65 in BKE_object_handle_data_update (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/object_update.c:202
#13 0x00000000037d196b in BKE_object_eval_uber_data (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088)
--Type <RET> for more, q to quit, c to continue without paging--
   lender-git/blender/source/blender/blenkernel/intern/object_update.c:395
#14 0x0000000005d09b4d in blender::deg::DepsgraphNodeBuilder::<lambda(Depsgraph*)>::operator()(Depsgraph *) const
    (__closure=0x6110016da248, depsgraph=0x61a00010aa88)
    at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1485
#15 0x0000000005d2dabd in std::_Function_handler<void(Depsgraph*), blender::deg::DepsgraphNodeBuilder::build_object_data_geometry(Object*, bool)::<lambda(Depsgraph*)> >::_M_invoke(const std::_Any_data &, Depsgraph *&&) (__functor=..., __args#0=@0x7fffbc7a1830: 0x61a00010aa88)
    at /usr/include/c++/9/bits/std_function.h:300
#16 0x0000000005c666c9 in std::function<void (Depsgraph*)>::operator()(Depsgraph*) const (this=0x6110016da248, __args#0=0x7fffbc7a18a0)
    at /usr/include/c++/9/bits/std_function.h:688
#17 0x0000000005c61ab2 in blender::deg::(anonymous namespace)::evaluate_node(blender::deg::(anonymous namespace)::DepsgraphEvalState const*, blender::deg::OperationNode*) (state=0x7fffffffd880, operation_node=0x6110016da188)
    at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:118
#18 0x0000000005c61b01 in blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*)
    (pool=0x61300062b2c8, taskdata=0x6110016da188)
    at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:129
#19 0x000000001b53b7c0 in Task::operator()() const (this=0x613000210ac8)
    at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/task_pool.cc:178
#20 0x000000001b53eeda in tbb::internal::function_task<Task>::execute() (this=0x613000210ac0)
    at /mnt/data/Devel/blender-git/lib/linux_centos7_x86_64/tbb/include/tbb/task.h:1059
- 21 0x0000000005135475 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) ()
- 22 0x000000000513572b in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*)
    ()
- 23 0x0000000005124327 in tbb::internal::arena::process(tbb::internal::generic_scheduler&) ()
- 24 0x000000000512f160 in tbb::internal::market::process(rml::job&) ()
- 25 0x000000000513119c in tbb::internal::rml::private_worker::run() ()
- 26 0x0000000005131399 in tbb::internal::rml::private_worker::thread_routine(void*) ()
- 27 0x00007ffff7546609 in start_thread (arg=<optimized out>) at pthread_create.c:477
- 28 0x00007ffff6ecf293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

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.983989,
"duplicate_report_number": "91809"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Geometry nodes (Fields) Assertion failed at input_has_attribute_toggle()</summary> 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: ``` BLI_assert failed: source/blender/modifiers/intern/MOD_nodes.cc:320, input_has_attribute_toggle(), at 'node_tree.field_inferencing_interface != nullptr' ``` **Exact steps for others to reproduce the error** 1. Start blender 2. Enter geometry nodes workspace 3. Click New to create a new GN modifier 3. Add a new Math node 4. Connect a new output socket from Group Input into the first socket of the Math node 5. Click on empty space to deselect nodes 6. Hit Ctrl+Z 7. Crash Stack trace: ``` - 0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 - 1 0x00007ffff6dd2859 in __GI_abort () at abort.c:79 - 2 0x000000001aff98ae in _BLI_assert_abort () at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/BLI_assert.c:61 - 3 0x000000000631e3f2 in input_has_attribute_toggle(bNodeTree const&, int) (node_tree=..., socket_index=1) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:320 #4 0x0000000006325d2b in initialize_group_input(NodesModifierData&, blender::nodes::OutputSocketRef const&, void*) (nmd=..., socket=..., r_value=0x60e000097498) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:693 #5 0x000000000632b95d in compute_geometry(blender::nodes::DerivedNodeTree const&, blender::Span<blender::nodes::NodeRef const*>, blender::nodes::NodeRef const&, GeometrySet, NodesModifierData*, ModifierEvalContext const*) (tree=..., group_input_nodes=..., output_node=..., input_geometry_set=..., nmd=0x60f000191cb8, ctx=0x7fffbc7a0bd0) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:934 #6 0x000000000632de20 in modifyGeometry(ModifierData*, ModifierEvalContext const*, GeometrySet&) (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=...) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1066 #7 0x000000000632e768 in modifyGeometrySet(ModifierData*, ModifierEvalContext const*, GeometrySet*) (md=0x60f000191cb8, ctx=0x7fffbc7a0bd0, geometry_set=0x7fffbc7a0ed0) at /mnt/data/Devel/blender-git/blender/source/blender/modifiers/intern/MOD_nodes.cc:1093 #8 0x0000000004902d86 in modifier_modify_mesh_and_geometry_set(ModifierData*, ModifierEvalContext const&, Mesh*, GeometrySet&) (md=0x60f000191cb8, mectx=..., input_mesh=0x61c00011f088, geometry_set=...) at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:953 #9 0x00000000049067df in mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**) (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, use_deform=true, need_mapping=false, dataMask=0x7fffbc7a15a0, index=-1, use_cache=true, allow_shared_mesh=true, r_deform=0x7fffbc7a14a0, r_final=0x7fffbc7a1480, r_geometry_set=0x7fffbc7a14c0) at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1291 #10 0x000000000490da2b in mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool) (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, dataMask=0x7fffbc7a15a0, need_mapping=false) at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:1914 #11 0x000000000490f684 in makeDerivedMesh(Depsgraph*, Scene*, Object*, BMEditMesh*, CustomData_MeshMasks const*) (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088, em=0x0, dataMask=0x7fffbc7a16c0) at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/DerivedMesh.cc:2061 #12 0x00000000037cee65 in BKE_object_handle_data_update (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088) at /mnt/data/Devel/blender-git/blender/source/blender/blenkernel/intern/object_update.c:202 #13 0x00000000037d196b in BKE_object_eval_uber_data (depsgraph=0x61a00010aa88, scene=0x62300007fd08, ob=0x61a00010b088) --Type <RET> for more, q to quit, c to continue without paging-- lender-git/blender/source/blender/blenkernel/intern/object_update.c:395 #14 0x0000000005d09b4d in blender::deg::DepsgraphNodeBuilder::<lambda(Depsgraph*)>::operator()(Depsgraph *) const (__closure=0x6110016da248, depsgraph=0x61a00010aa88) at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1485 #15 0x0000000005d2dabd in std::_Function_handler<void(Depsgraph*), blender::deg::DepsgraphNodeBuilder::build_object_data_geometry(Object*, bool)::<lambda(Depsgraph*)> >::_M_invoke(const std::_Any_data &, Depsgraph *&&) (__functor=..., __args#0=@0x7fffbc7a1830: 0x61a00010aa88) at /usr/include/c++/9/bits/std_function.h:300 #16 0x0000000005c666c9 in std::function<void (Depsgraph*)>::operator()(Depsgraph*) const (this=0x6110016da248, __args#0=0x7fffbc7a18a0) at /usr/include/c++/9/bits/std_function.h:688 #17 0x0000000005c61ab2 in blender::deg::(anonymous namespace)::evaluate_node(blender::deg::(anonymous namespace)::DepsgraphEvalState const*, blender::deg::OperationNode*) (state=0x7fffffffd880, operation_node=0x6110016da188) at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:118 #18 0x0000000005c61b01 in blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*) (pool=0x61300062b2c8, taskdata=0x6110016da188) at /mnt/data/Devel/blender-git/blender/source/blender/depsgraph/intern/eval/deg_eval.cc:129 #19 0x000000001b53b7c0 in Task::operator()() const (this=0x613000210ac8) at /mnt/data/Devel/blender-git/blender/source/blender/blenlib/intern/task_pool.cc:178 #20 0x000000001b53eeda in tbb::internal::function_task<Task>::execute() (this=0x613000210ac0) at /mnt/data/Devel/blender-git/lib/linux_centos7_x86_64/tbb/include/tbb/task.h:1059 - 21 0x0000000005135475 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) () - 22 0x000000000513572b in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) () - 23 0x0000000005124327 in tbb::internal::arena::process(tbb::internal::generic_scheduler&) () - 24 0x000000000512f160 in tbb::internal::market::process(rml::job&) () - 25 0x000000000513119c in tbb::internal::rml::private_worker::run() () - 26 0x0000000005131399 in tbb::internal::rml::private_worker::thread_routine(void*) () - 27 0x00007ffff7546609 in start_thread (arg=<optimized out>) at pthread_create.c:477 - 28 0x00007ffff6ecf293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ``` </details> <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 32.983989, "duplicate_report_number": "91809" } </details>

👍 1

Triager-bot commented 2026-04-12 17:54:10 +00:00

Author

Owner

Copy Link

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: 65d5b94740d3
Worked: 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

• Download the attached .blend file and put it in a asset library (E.g. The default asset library in your documents folder)
• Open new file, select a mesh, switch to edit mode, and run the Geometry nodes tool called Tool from the top of the 3D viewport.
• In the redo panel in the bottom left of the 3D viewport, adjust a value and Blender will crash.

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.635906,
"duplicate_report_number": "147236"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>GN Tools Crashes - input values modification</summary> 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: `65d5b94740d3` Worked: 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** - Download the attached .blend file and put it in a asset library (E.g. The default asset library in your documents folder) - Open new file, select a mesh, switch to edit mode, and run the Geometry nodes tool called `Tool` from the top of the 3D viewport. - In the redo panel in the bottom left of the 3D viewport, adjust a value and Blender will crash. </details> <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 14.635906, "duplicate_report_number": "147236" } </details>

👍 1

Triager-bot commented 2026-04-12 17:54:23 +00:00

Author

Owner

Copy Link

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: b5ea0d2f41

Short 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

• Open attached .blend file
• Navigate to Geometry Nodes
• Drop the "Simulation Input"-Node after the Curve Circle

{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.793653,
"duplicate_report_number": "102790"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Crash on adding "Simulation Input"-Node to geometry</summary> 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: `b5ea0d2f41` **Short 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** * Open attached .blend file * Navigate to Geometry Nodes * Drop the "Simulation Input"-Node after the Curve Circle {[F13971604](https://archive.blender.org/developer/F13971604/grafik.png), size=full} [simulation_node_crash.blend](https://archive.blender.org/developer/F13971595/simulation_node_crash.blend) Sorry if this has already been reported but I couldn't find any other report with this problem. Thanks! </details> <details> <summary>LLM Reasoning</summary> 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. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.793653, "duplicate_report_number": "102790" } </details>

👍 1

Triager-bot added

Status

Good judgement

and removed

Status

Needs review

labels 2026-04-13 14:16:32 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

No results found.

No results found.

Labels

Clear labels

Status

Bad Judgement

Status

Good judgement

Status

Needs review

Status

Uncertain Judgement

Trager-Bot Will Send Comment

No Label

Status

Good judgement

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

Triager-bot

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Triager-bot/blender-bug-reports#52