Naming attribute in multiple geometry nodes modifier causes blender to crash #93782

New Issue

Godwin Jimoh · 2021-12-07T00:48:23+01:00

Godwin Jimoh commented

2021-12-07 00:48:23 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11

Blender Version
Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557
Worked: (newest version of Blender that worked as expected)

Short description of error
When I stack up multiple geometry node modifiers with node groups similar to the one below and try to rename the output attributes then blender crashes.

this is the error from the console

Exact steps for others to reproduce the error

open this blend file: output attribute bug.blend or set up the same node group from the picture above
Duplicate the geometry nodes modifier up to 5 times
Try to rename the output attributes in the modifier panel of each of the geometry nodes modifier and then blender crashes

Some things to note about this bug:

The error only happens when the geometry being instanced are curve objects. mesh works just fine.
The attribute output does not need to be connected to anything. Just that they must be named in the modifier panel and they must be at least two outputs beyond just the geometry output.
The bug goes away when the Realize Instance node is removed.
The crash is triggered when you duplicate the geo nodes modifier and try to rename the output. (It does not matter if it's duplicated or a new node group. as long as it meets the criteria above it will eventually crash)
The previous step must be repeated like 2 to 3 (at most 5) times before there’s a crash (at least on my end).
I can stack the same geometry nodes modifier with the same node group over and over as many times as I like. The crash only happens when I try to enter the name of the output attribute in the modifier panel.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11 **Blender Version** Broken: version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `f1cca30557` Worked: (newest version of Blender that worked as expected) **Short description of error** When I stack up multiple geometry node modifiers with node groups similar to the one below and try to rename the output attributes then blender crashes. ![output attribute bug.png](https://archive.blender.org/developer/F12700841/output_attribute_bug.png) this is the error from the console ![crash report.jpg](https://archive.blender.org/developer/F12700848/crash_report.jpg) **Exact steps for others to reproduce the error** 1. open this blend file: [output attribute bug.blend](https://archive.blender.org/developer/F12700856/output_attribute_bug.blend) or set up the same node group from the picture above 2. Duplicate the geometry nodes modifier up to 5 times 3. Try to rename the output attributes in the modifier panel of each of the geometry nodes modifier and then blender crashes **Some things to note about this bug:** - The error only happens when the geometry being instanced are curve objects. mesh works just fine. - The attribute output does not need to be connected to anything. Just that they must be named in the modifier panel and they must be at least two outputs beyond just the geometry output. - The bug goes away when the Realize Instance node is removed. - The crash is triggered when you duplicate the geo nodes modifier and try to rename the output. (It does not matter if it's duplicated or a new node group. as long as it meets the criteria above it will eventually crash) - The previous step must be repeated like 2 to 3 (at most 5) times before there’s a crash (at least on my end). - I can stack the same geometry nodes modifier with the same node group over and over as many times as I like. The crash only happens when I try to enter the name of the output attribute in the modifier panel.

Godwin Jimoh commented

2021-12-07 00:48:23 +01:00

Added subscriber: @Astronet-4

blender-admin commented

2021-12-07 00:48:23 +01:00

#94106 was marked as duplicate of this issue

Pratik Borhade commented

2021-12-07 20:18:50 +01:00

Added subscriber: @PratikPB2123

Jacques Lucke commented

2021-12-11 12:20:08 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2021-12-11 12:20:08 +01:00

I can reproduce it in 3.0 but not in master. It seems to be a problem with joining curves.
Backtrace: P2657.
It asserts when calling assert_valid_point_attributes.
In master that was probably fixed by 506d672524, can someone confirm that?

I can reproduce it in 3.0 but not in master. It seems to be a problem with joining curves. Backtrace: [P2657](https://archive.blender.org/developer/P2657.txt). It asserts when calling `assert_valid_point_attributes`. In master that was probably fixed by 506d672524, can someone confirm that?

Jacques Lucke commented

2021-12-15 13:26:13 +01:00

Added subscriber: @JoseConseco

Pratik Borhade commented

2021-12-15 13:41:52 +01:00

can someone confirm that?

@JacquesLucke , sure. I will check

Fix lies between 88e9e97ee9 - fed4fc9c42 so probably 506d672524 has fixed the crash? I will confirm with git bisect.

> can someone confirm that? @JacquesLucke , sure. I will check Fix lies between 88e9e97ee907 - fed4fc9c42d2 so probably `506d672524` has fixed the crash? I will confirm with git bisect.

Pratik Borhade commented

2021-12-15 14:23:17 +01:00

Yes, on master crash was fixed by 506d672524

3.0.0 is still broken.

Yes, on master crash was fixed by 506d672524 3.0.0 is still broken.

Pratik Borhade commented

2021-12-17 13:09:30 +01:00

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

Pratik Borhade commented

2021-12-17 13:09:30 +01:00

3.0.0 is still broken.

@JacquesLucke , would it be safe to backport 506d672524?

Confirming for now because crash persists on 3.0.0 branch. (Feel free to reset status)

> 3.0.0 is still broken. @JacquesLucke , would it be safe to backport 506d672524? Confirming for now because crash persists on 3.0.0 branch. (Feel free to reset status)

Jacques Lucke commented

2021-12-17 13:18:58 +01:00

Yes, I think backporting this commit should be safe. It would only not be safe if the realize-instances code in 3.0 has a bug as well (which we haven't found yet afaik). However, if such a bug exists, it should be fixed anyway.

Godwin Jimoh commented

2022-01-05 11:40:28 +01:00

The same "EXCEPTION_ACCESS_VIOLATION" error seems to show up in a geometry nodes bug I just reported: #94659. This time it is triggered when the collection Info node and the Separate Geometry node are connected together under certain conditions

The same "**EXCEPTION_ACCESS_VIOLATION**" error seems to show up in a geometry nodes bug I just reported: #94659. This time it is triggered when the **collection Info** node and the **Separate Geometry** node are connected together under certain conditions

Bastien Montagne commented

2022-01-27 16:30:25 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2022-01-27 16:30:25 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Bastien Montagne closed this issue

2022-01-27 16:30:25 +01:00

Bastien Montagne self-assigned this 2022-01-27 16:30:25 +01:00

Bastien Montagne commented

2022-01-27 16:30:25 +01:00

Will consider this issue as resolved since it is fixed in master. Unfortunately it seems it missed the 3.0.1 corrective release though?

Thomas Dinges added this to the 3.0 milestone 2023-02-08 15:58:47 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Naming attribute in multiple geometry nodes modifier causes blender to crash #93782