Regression: Specific Geometry Nodes tree (involving curve nodes) crashes with specific input mesh #102144

New Issue

Will · 2022-10-29T16:08:48+02:00

Will commented

2022-10-29 16:08:48 +02:00

System Information
Operating system: Linux
Graphics card: Intel

Blender Version
Broken: blender-3.3.1-linux-x64.tar.xz, blender-3.2.2-linux-x64, blender-3.2.1-linux-x64
Worked: blender-3.1.2-linux-x64, blender-3.2.0-alpha+master.95005bbe02cf-linux.x86_64-release

Apparently caused by 2d80f814cc

This is dependent both the specific node setup (mesh-to-curve, set-handle-type, set-spline-resolution [with a value of zero!] all seem to be necessary to trigger the bug) but the input mesh as well (simple plane crashes, but simple cube is fine

Exact steps for others to reproduce the error

GeomNodesCrash_simplified2.blend

open blend
Cube with enabled GN modifier
Plane with same GN modifier (disabled)
enable modifier on Plane >> crash
you can also extrude an edge from the Plane prior to enabling the modifier on the Plane >> no crash anymore

Original report

I have a project that always crashes when I try to load it in newer versions of Blender.
It has lots of drivers, modifiers, and procedural geometry.
The crash appears to be tied to a specific Geometry Nodes tree.

Download the attached file:

GeomNodesCrash.blend

Try to open it in one of the affected Blender versions.
Observe crash.

If the file is opened in an unaffected version and the CRASH_CAUSING_NODEGROUP is completely removed from it (SHIFT+LMB on the Unlink "X"), then the crash does not happen.

Also: crash.txt:

crash.txt

gdb bt looks like it's saying the same things.

**System Information** Operating system: Linux Graphics card: Intel **Blender Version** Broken: `blender-3.3.1-linux-x64.tar.xz`, `blender-3.2.2-linux-x64`, `blender-3.2.1-linux-x64` Worked: `blender-3.1.2-linux-x64`, `blender-3.2.0-alpha+master.95005bbe02cf-linux.x86_64-release` Apparently caused by 2d80f814cc This is dependent both the specific node setup (mesh-to-curve, set-handle-type, set-spline-resolution [with a value of zero!] all seem to be necessary to trigger the bug) but the input mesh as well (simple plane crashes, but simple cube is fine **Exact steps for others to reproduce the error** [GeomNodesCrash_simplified2.blend](https://archive.blender.org/developer/F13831865/GeomNodesCrash_simplified2.blend) - open blend - `Cube` with enabled GN modifier - `Plane` with same GN modifier (disabled) - enable modifier on `Plane` >> crash - you can also extrude an edge from the Plane prior to enabling the modifier on the Plane >> no crash anymore **Original report** I have a project that always crashes when I try to load it in newer versions of Blender. It has lots of drivers, modifiers, and procedural geometry. The crash appears to be tied to a specific Geometry Nodes tree. 1. Download the attached file: [GeomNodesCrash.blend](https://archive.blender.org/developer/F13807033/GeomNodesCrash.blend) 2. Try to open it in one of the affected Blender versions. 3. Observe crash. If the file is opened in an unaffected version and the `CRASH_CAUSING_NODEGROUP` is completely removed from it (`SHIFT`+`LMB` on the Unlink "X"), then the crash does not happen. Also: `crash.txt`: [crash.txt](https://archive.blender.org/developer/F13797488/crash.txt) `gdb` `bt` looks like it's saying the same things.

Will commented

2022-10-29 16:08:48 +02:00

Added subscriber: @WCN

Jesse Yurkovich commented

2022-10-30 02:49:09 +01:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2022-10-30 02:49:09 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Jesse Yurkovich commented

2022-10-30 02:49:09 +01:00

Unfortunately the stack trace does not tell us much. We'll need a way to reproduce the issue in order to fix it. Is is possible to modify the original file in a way that is shareable? Replace geometry with simple primitives, remove textures entirely or replace with small, solid colors, textures?

Will changed title from ~~Segfault loading file from 3.0.0.~~ to Crash loading geometry nodes from 3.0.0.

2022-10-30 12:18:26 +01:00

Will commented

2022-10-30 12:26:29 +01:00

@deadpin Yeah, I find myself in this position often enough that I decided to write a quick script to mangle all the impactful data. File added.

Looks like a specific geometry nodes tree is causing the problem.

@deadpin Yeah, I find myself in this position often enough that I decided to write a quick script to mangle all the impactful data. File added. Looks like a specific geometry nodes tree is causing the problem.

Iliya Katushenock commented

2022-10-30 12:34:32 +01:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2022-10-30 12:34:32 +01:00

Potentially related.
#101972

Potentially related. #101972

Iliya Katushenock commented

2022-10-30 12:35:34 +01:00

But it will still be better if you can simplify the example file as much as possible.

Jesse Yurkovich commented

2022-10-30 22:02:25 +01:00

Changed status from 'Needs User Info' to: 'Confirmed'

Jesse Yurkovich commented

2022-10-30 22:02:25 +01:00

Will confirm as I can reproduce the crash here as well. The stack is sufficiently different than the Spline bug so will keep this separate.

I won't have time today to bisect the issue; it seems to go very far back. Here is the Assert that happens with a Debug build because the result span is incorrect:

blender.exe!_BLI_assert_abort() Line 47	C
blender.exe!blender::bke::curves::bezier::evaluate_segment(..., blender::MutableSpan<blender::vec_base<float,3>> result) Line 212	C++
blender.exe!blender::bke::curves::bezier::calculate_evaluated_positions(..., blender::MutableSpan<blender::vec_base<float,3>> evaluated_positions) Line 254	C++
blender.exe!blender::bke::CurvesGeometry::evaluated_positions::__l2::<lambda_1>::()::__l2::<lambda_1>::operator()(blender::IndexRange curves_range) Line 686	C++
blender.exe!blender::threading::parallel_for<``blender::bke::CurvesGeometry::evaluated_positions'::`2'::<lambda_1>::operator()'::`2'::<lambda_1>>(...) Line 72	C++
blender.exe!blender::bke::CurvesGeometry::evaluated_positions::__l2::<lambda_1>::operator()() Line 663	C++
blender.exe!tbb::interface7::internal::delegated_function<`blender::bke::CurvesGeometry::evaluated_positions'::`2'::<lambda_1> const ,void>::operator()() Line 97	C++

Will confirm as I can reproduce the crash here as well. The stack is sufficiently different than the Spline bug so will keep this separate. I won't have time today to bisect the issue; it seems to go very far back. Here is the Assert that happens with a Debug build because the `result` span is incorrect: ``` blender.exe!_BLI_assert_abort() Line 47 C blender.exe!blender::bke::curves::bezier::evaluate_segment(..., blender::MutableSpan<blender::vec_base<float,3>> result) Line 212 C++ blender.exe!blender::bke::curves::bezier::calculate_evaluated_positions(..., blender::MutableSpan<blender::vec_base<float,3>> evaluated_positions) Line 254 C++ blender.exe!blender::bke::CurvesGeometry::evaluated_positions::__l2::<lambda_1>::()::__l2::<lambda_1>::operator()(blender::IndexRange curves_range) Line 686 C++ blender.exe!blender::threading::parallel_for<``blender::bke::CurvesGeometry::evaluated_positions'::`2'::<lambda_1>::operator()'::`2'::<lambda_1>>(...) Line 72 C++ blender.exe!blender::bke::CurvesGeometry::evaluated_positions::__l2::<lambda_1>::operator()() Line 663 C++ blender.exe!tbb::interface7::internal::delegated_function<`blender::bke::CurvesGeometry::evaluated_positions'::`2'::<lambda_1> const ,void>::operator()() Line 97 C++ ```

Iliya Katushenock commented

2022-10-30 22:10:30 +01:00

Yes, I also received a stack, and because of it I realized that the error is related to the curves in the nodes. But yes, it's not the same mistake. Just a suspicion.

Will commented

2022-10-30 23:31:26 +01:00

3.2.1 is broken. 3.1.2 works.

In the 3.2 branch, 95005bbe02 also works.

3.2.1 is broken. 3.1.2 works. In the 3.2 branch, 95005bbe02cf also works.

Philipp Oeser commented

2022-11-01 11:16:09 +01:00

Added subscribers: @HooglyBoogly, @lichtwerk

Philipp Oeser commented

2022-11-01 11:16:09 +01:00

Apparently caused by 2d80f814cc

This is dependent both the specific node setup (mesh-to-curve, set-handle-type, set-spline-resolution [with a value of zero!] all seem to be necessary to trigger the bug) but the input mesh as well (simple plane crashes, but simple cube is fine

Here is a simplified file:
GeomNodesCrash_simplified2.blend

open blend
Cube with enabled GN modifier
Plane with same GN modifier (disabled)
enable modifier on Plane >> crash
you can also extrude an edge from the Plane prior to enabling the modifier on the Plane >> no crash anymore

@HooglyBoogly : mind checking?

Apparently caused by 2d80f814cc This is dependent both the specific node setup (mesh-to-curve, set-handle-type, set-spline-resolution [with a value of zero!] all seem to be necessary to trigger the bug) but the input mesh as well (simple plane crashes, but simple cube is fine Here is a simplified file: [GeomNodesCrash_simplified2.blend](https://archive.blender.org/developer/F13831865/GeomNodesCrash_simplified2.blend) - open blend - `Cube` with enabled GN modifier - `Plane` with same GN modifier (disabled) - enable modifier on `Plane` >> crash - you can also extrude an edge from the Plane prior to enabling the modifier on the Plane >> no crash anymore @HooglyBoogly : mind checking?

Philipp Oeser changed title from ~~Crash loading geometry nodes from 3.0.0.~~ to Regression: Specific Geometry Nodes tree (involving curve nodes) crashes with specific input mesh

2022-11-01 11:19:53 +01:00

blender-admin commented

2022-11-06 15:36:53 +01:00

This issue was referenced by 0697631929

This issue was referenced by 0697631929d9ec4be92feae9b8347dd1e32c6ddd

Jacques Lucke commented

2022-11-06 15:37:11 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Jacques Lucke closed this issue

2022-11-06 15:37:11 +01:00

Jacques Lucke self-assigned this 2022-11-06 15:37:11 +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

Regression: Specific Geometry Nodes tree (involving curve nodes) crashes with specific input mesh #102144