Blender Crash with Complex Geometry Nodes Group #124391

Closed
opened 2024-07-09 09:41:15 +02:00 by Jas9r · 17 comments

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99

Blender Version
Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 19:36, hash: d527e3a6bd78
Broken: 4.1.1
Worked: 4.0.2

looks like it is caused by 7bd509f73a

Short description of error
The attached blend file consists of just the default cube with a complex geometry node group added to.
Blender always crashes within a few seconds of initiating playback. The crash also occurs consistently after modifying the values in the Geometry Nodes modifier.

Exact steps for others to reproduce the error
Open the attached blend file and initiate playback.

**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 555.99 **Blender Version** Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 19:36, hash: `d527e3a6bd78` Broken: 4.1.1 Worked: 4.0.2 looks like it is caused by 7bd509f73a97d350cbc06dcda715a7932a2b5263 **Short description of error** The attached blend file consists of just the default cube with a complex geometry node group added to. Blender always crashes within a few seconds of initiating playback. The crash also occurs consistently after modifying the values in the Geometry Nodes modifier. **Exact steps for others to reproduce the error** Open the attached blend file and initiate playback.
Jas9r added the
Type
Report
Status
Needs Triage
Severity
Normal
labels 2024-07-09 09:41:15 +02:00

I can confirm read after free in code of modifier after geometry nodes execute.

I can confirm read after free in code of modifier after geometry nodes execute.

Without real-world case of this bug, this will not be considered as high priority bug for me.

Without real-world case of this bug, this will not be considered as high priority bug for me.
Iliya Katushenock added this to the 4.2 LTS milestone 2024-07-09 10:06:32 +02:00

To me it seems a very recent regression.
Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 19:36, hash: d527e3a6bd78
Worked: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-06 04:49, hash: 11b1919bcfe3

I haven't tested other versions to see if this can be an accident or whatever.
but I am very discouraged with this large node group.
I would encourage the reporter to simplify the file, otherwise investing resources in debugging seems pointless and harmful.

To me it seems a very recent regression. Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-08 19:36, hash: `d527e3a6bd78` Worked: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-07-06 04:49, hash: `11b1919bcfe3` I haven't tested other versions to see if this can be an accident or whatever. but I am very discouraged with this large node group. I would encourage the reporter to simplify the file, otherwise investing resources in debugging seems pointless and harmful.

I can reproduce this in version: 4.2.0 Alpha, branch: main, commit date: 2024-04-26 21:19, hash: d11c6962b099

I can reproduce this in version: 4.2.0 Alpha, branch: main, commit date: 2024-04-26 21:19, hash: `d11c6962b099`
Author

Hello, I would also like to add that this is an obfuscated version of a product (Advanced Array Tool) that I sell online, with a significant user base.

Hello, I would also like to add that this is an obfuscated version of a product (Advanced Array Tool) that I sell online, with a significant user base.

Is there is real-world version of that what we can test and see the same issue (without such a lot of spaghetti)?

Is there is real-world version of that what we can test and see the same issue (without such a lot of spaghetti)?

My opinion doesn't change. whether it's a real world case or fake sample case, I think it should be simplified.

My opinion doesn't change. whether it's a real world case or fake sample case, I think it should be simplified.
Author

I'm unable to share it publicly since it's a commercial product available online. However, I'd be happy to provide it via email. Please let me know if you'd like me to send it to you privately.

I'm unable to share it publicly since it's a commercial product available online. However, I'd be happy to provide it via email. Please let me know if you'd like me to send it to you privately.

Better to create a (similar) new one with free license.

Better to create a (similar) new one with free license.

I'm unable to share it publicly since it's a commercial product available online. However, I'd be happy to provide it via email. Please let me know if you'd like me to send it to you privately.

It's probably discouraged due to many reasons. for example, other developers must also have it to know what's wrong.
And more importantly, likely someone still have to simplify the file to investigate. It's a matter costing your time or many other people's time in investigating.

> I'm unable to share it publicly since it's a commercial product available online. However, I'd be happy to provide it via email. Please let me know if you'd like me to send it to you privately. It's probably discouraged due to many reasons. for example, other developers must also have it to know what's wrong. And more importantly, likely someone still have to simplify the file to investigate. It's a matter costing your time or many other people's time in investigating.
Author

Simplifying the file doesn't help it. The crashes occur less often as I remove nodes, almost never crashing with fewer than 900 nodes. Adding many reroute nodes also reduces crashes. The crash doesn't seem to be caused by a specific set of nodes but rather by the extensive calculations involved. This "spaghetti" node group worked well in Blender 4.1.0 Beta until something broke. Also creating a new one would be extremely time-consuming.

Simplifying the file doesn't help it. The crashes occur less often as I remove nodes, almost never crashing with fewer than 900 nodes. Adding many reroute nodes also reduces crashes. The crash doesn't seem to be caused by a specific set of nodes but rather by the extensive calculations involved. This "spaghetti" node group worked well in Blender 4.1.0 Beta until something broke. Also creating a new one would be extremely time-consuming.
Member

Bisect will probably help, will do...

Bisect will probably help, will do...
Member

Worked: 4.0.2

@Jas9r : could we have a file that actually outputs something in 4.0.2?

For me, that nodetree outputs empty geometry in 4.0.2

And btw. : it does not seem to crash in a lite build for me (28c3332e32), whereas a regular build crashes

>Worked: 4.0.2 @Jas9r : could we have a file that actually outputs something in 4.0.2? For me, that nodetree outputs empty geometry in 4.0.2 And btw. : it does not seem to crash in a lite build for me (28c3332e32b7072b559ae4086412ce6b44176a17), whereas a regular build crashes
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Confirmed
labels 2024-07-10 10:04:27 +02:00

I had the crash in lite debug build\

I had the crash in lite debug build\
Author

@lichtwerk Yes, here's a version saved in 3.6.4

@lichtwerk Yes, here's a version saved in 3.6.4
Member

OK, will bisect (broke between good b469d9dd7d and bad e246c111fb it seems -- 7bd509f73a seems like a culprit candidate?)

Note: before the crash we are getting:

-> Modifier: GeometryNodes 	(hash: 0xb7506a1744781b02387e24fb9e8dc997)
Missing outputs:
  Output
OK, will bisect (broke between good b469d9dd7dc5 and bad e246c111fba6 it seems -- 7bd509f73a97d350cbc06dcda715a7932a2b5263 seems like a culprit candidate?) Note: before the crash we are getting: ``` -> Modifier: GeometryNodes (hash: 0xb7506a1744781b02387e24fb9e8dc997) Missing outputs: Output ```
Philipp Oeser added
Status
Confirmed
and removed
Status
Needs Information from User
labels 2024-07-10 12:38:32 +02:00
Member

Yeah, looks like it is caused by 7bd509f73a

@JacquesLucke : mind checking? (I am aware the noodles are a mess in their current state, but maybe you find something?)

I will also dare setting prio to High for now (since this is a crasher)

Yeah, looks like it is caused by 7bd509f73a97d350cbc06dcda715a7932a2b5263 @JacquesLucke : mind checking? (I am aware the noodles are a mess in their current state, but maybe you find something?) I will also dare setting prio to High for now (since this is a crasher)
Philipp Oeser added
Severity
High
and removed
Severity
Normal
labels 2024-07-10 13:14:46 +02:00
Blender Bot added
Status
Resolved
and removed
Status
Confirmed
labels 2024-07-10 18:01:04 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
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
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#124391
No description provided.